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
@@ -11,7 +11,7 @@ Autodesk provides a simple Python-based API for accessing Flow Production Tracki
11
11
The latest version can always be found at https://github.com/shotgunsoftware/python-api
12
12
13
13
## Documentation
14
-
Tutorials and detailed documentation about the Python API are available at http://developer.shotgridsoftware.com/python-api).
14
+
Tutorials and detailed documentation about the Python API are available at http://developer.shotgridsoftware.com/python-api.
15
15
16
16
Some useful direct links:
17
17
@@ -31,12 +31,11 @@ You can see the [full history of the Python API on the documentation site](http:
31
31
Integration and unit tests are provided.
32
32
33
33
- All tests require:
34
-
- The [nose unit testing tools](http://nose.readthedocs.org),
35
-
- The [nose-exclude nose plugin](https://pypi.org/project/nose-exclude/)
36
-
- (Note: Running `pip install -r tests/ci_requirements.txt` will install this package)
34
+
-[pytest](https://docs.pytest.org/) and related plugins
35
+
- (Note: Running `pip install -r tests/requirements.txt` will install all required packages)
37
36
- A `tests/config` file (you can copy an example from `tests/example_config`).
38
-
- Tests can be run individually like this: `nosetests --config="nose.cfg" tests/test_client.py`
39
-
- Make sure to not forget the `--config="nose.cfg"` option. This option tells nose to use our config file.
40
-
-`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).
37
+
- Tests can be run individually like this: `pytest tests/test_client.py`
38
+
- To run all tests: `pytest`
39
+
- To run tests with coverage: `pytest --cov shotgun_api3 --cov-report html`
40
+
-`test_client` and `test_unit` use mock server interaction and do not require a Flow Production Tracking instance to be available (no modifications to `tests/config` are necessary).
41
41
-`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.
42
-
- To run all of the tests, use the shell script `run-tests`.
0 commit comments