You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/pages/04-web-development/35-testing.markdown
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,8 @@ test runners, coverage reports and related libraries.
56
56
Requests library with Selenium to make it easier to run automated
57
57
browser tests.
58
58
59
+
*[coverage.py](https://coverage.readthedocs.io/) is a tool for
60
+
measuring code coverage when running tests.
59
61
60
62
61
63
### Testing resources
@@ -95,19 +97,32 @@ test runners, coverage reports and related libraries.
95
97
[top answer on Stack Overflow](http://stackoverflow.com/questions/4904096/whats-the-difference-between-unit-functional-acceptance-and-integration-test)
96
98
to that very question.
97
99
100
+
*[The cleaning hand of Pytest](https://blog.daftcode.pl/the-cleaning-hand-of-pytest-28f434f4b684)
101
+
provides a couple of case studies for how companies set up their testing
102
+
systems. It then gives the boilerplate code the author uses for Pytest
103
+
and goes through a bunch of code samples for common situations.
104
+
98
105
*[Using pytest with Django](http://engineroom.trackmaven.com/blog/using-pytest-with-django/)
99
106
shows how to get a basic [pytest](http://pytest.org/latest/) test
100
107
running for a Django project and explains why the author prefers pytest
101
108
over standard unittest testing.
102
109
103
-
*[Distributed Testing with Selenium Grid and Docker](https://testdriven.io/distributed-testing-with-selenium-grid) shows how to distribute automated, browser tests with Selenium Grid and Docker Swarm. It also looks at how to run tests against a number of browsers and automate the provisioning and deprovisioning of machines to keep costs down.
110
+
*[Distributed Testing with Selenium Grid and Docker](https://testdriven.io/distributed-testing-with-selenium-grid)
111
+
shows how to distribute automated, browser tests with Selenium Grid and
112
+
Docker Swarm. It also looks at how to run tests against a number of
113
+
browsers and automate the provisioning and deprovisioning of machines to
114
+
keep costs down.
104
115
105
116
*[Principles of Automated Testing](http://www.lihaoyi.com/post/PrinciplesofAutomatedTesting.html)
106
117
explains how to prioritize what to test, goes through some levels of
107
118
testing from [unit](/unit-testing.html) to
108
119
[integration](/integration-testing.html) and examines when to use example
0 commit comments