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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Integration and unit tests are provided.
43
43
- (Note: Running `pip install -r tests/ci_requirements.txt` will install this package)
44
44
- A `tests/config` file (you can copy an example from `tests/example_config`).
45
45
- Tests can be run individually like this: `nosetests --config="nose.cfg" tests/test_client.py`
46
-
- Make sure to not forget the `--config="nose.cfg"` option. This option tells nose to use our config file. This will exclude python 2- and 3-specific files in the `/lib` directory, preventing a failure from being reported by nose for compilation due to incompatible syntax in those files.
46
+
- Make sure to not forget the `--config="nose.cfg"` option. This option tells nose to use our config file. This will exclude python 3-specific files in the `/lib` directory, preventing a failure from being reported by nose for compilation due to incompatible syntax in those files.
47
47
-`test_client` and `tests_unit` use mock server interaction and do not require a Flow Production Tracking instance to be available (no modifications to `tests/config` are necessary).
48
48
-`test_api` and `test_api_long`*do* require a Flow Production Tracking instance, with a script key available for the tests. The server and script user values must be supplied in the `tests/config` file. The tests will add test data to your server based on information in your config. This data will be manipulated by the tests, and should not be used for other purposes.
49
49
- To run all of the tests, use the shell script `run-tests`.
0 commit comments