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
+20-1Lines changed: 20 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,6 +97,10 @@ test runners, coverage reports and related libraries.
97
97
[top answer on Stack Overflow](http://stackoverflow.com/questions/4904096/whats-the-difference-between-unit-functional-acceptance-and-integration-test)
98
98
to that very question.
99
99
100
+
*[Testing Python applications with Pytest](https://semaphoreci.com/community/tutorials/testing-python-applications-with-pytest)
101
+
walks through the basics of using Pytest and some more advanced
102
+
ways to use it such as continuous testing through Semiphore CI.
103
+
100
104
*[The cleaning hand of Pytest](https://blog.daftcode.pl/the-cleaning-hand-of-pytest-28f434f4b684)
101
105
provides a couple of case studies for how companies set up their testing
102
106
systems. It then gives the boilerplate code the author uses for Pytest
@@ -106,7 +110,7 @@ test runners, coverage reports and related libraries.
106
110
shows how to get a basic [pytest](http://pytest.org/latest/) test
107
111
running for a Django project and explains why the author prefers pytest
108
112
over standard unittest testing.
109
-
113
+
110
114
*[Distributed Testing with Selenium Grid and Docker](https://testdriven.io/distributed-testing-with-selenium-grid)
111
115
shows how to distribute automated, browser tests with Selenium Grid and
112
116
Docker Swarm. It also looks at how to run tests against a number of
@@ -119,6 +123,21 @@ test runners, coverage reports and related libraries.
119
123
[integration](/integration-testing.html) and examines when to use example
120
124
and bulk tests.
121
125
126
+
*[How to run tests continuously while coding](https://www.blog.pythonlibrary.org/2017/03/14/how-to-run-python-tests-continuously-while-coding/)
127
+
contains a Python script that uses the
128
+
[watchdog](https://pythonhosted.org/watchdog/) to check for changes
129
+
to source code files in your project directory. If changes are detected
130
+
then your tests will be run to check that everything is still working
131
+
as intended.
132
+
133
+
* This test-driven development series shows you how to write an interpreter
134
+
in Python and contains a ton of great code samples to learn from:
135
+
136
+
*[A game of tokens: write an interpreter in Python with TDD - Part 1](http://blog.thedigitalcatonline.com/blog/2017/05/09/a-game-of-tokens-write-an-interpreter-in-python-with-tdd-part-1/)
137
+
*[A game of tokens - part 2](http://blog.thedigitalcatonline.com/blog/2017/10/01/a-game-of-tokens-write-an-interpreter-in-python-with-tdd-part-2/)
138
+
*[A game of tokens - part 3](http://blog.thedigitalcatonline.com/blog/2017/10/31/a-game-of-tokens-write-an-interpreter-in-python-with-tdd-part-3/)
139
+
*[A game of tokens - part 4](http://blog.thedigitalcatonline.com/blog/2018/06/02/a-game-of-tokens-write-an-interpreter-in-python-with-tdd-part-4/)
0 commit comments