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: source/developers/development_testing.markdown
+12-2Lines changed: 12 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,19 @@ $ tox
27
27
28
28
This will run unit tests against python 3.4 and 3.5 (if both are available locally), as well as run a set of tests which validate `pep8` and `pylint` style of the code.
29
29
30
-
You can optionally run tests on only one tox target using the `-e` option to select an environment.
30
+
#### {% linkable_title Testing Tips %}
31
31
32
-
For instance `tox -e lint` will run the linters only, `tox -e py34` will run unit tests only on python 3.4.
32
+
You can optionally run tests on only one tox target using the `-e` option to select an environment. For instance `tox -e lint` will run the linters only, `tox -e py34` will run unit tests only on python 3.4.
33
+
34
+
Tox uses virtual environments under the hood to create isolated testing environments. The Tox virtual environments will get out date when requirements change causing test errors. Run `tox -r` to create new Tox virtual environments.
35
+
36
+
During development on a specific file, it can speed up your workflow to just run tests and linting related to the file that you're working on. To run individual files:
0 commit comments