aa9dbf612e
* EventCallback object have order * callbacks are processed by the callback order * safer approach to get function information * modified docstring a little * added tests for ordered calbacks * fix python 2 support * added support for partial methods * removed unused '_get_func_info' * formatting fix * change test functions docstring * added test for removement of source function when partial is used * Allow order 'None' * implemented 'weakref_partial' to allow partial callbacks * minor tweaks * added support to pass additional arguments to 'wearkref_partial' * modify docstring * added 'weakref_partial' to tests * move public method before prive methods * added required order back but use '100' as default order * fix typo Co-authored-by: Roy Nieterau <roy_nieterau@hotmail.com> --------- Co-authored-by: Roy Nieterau <roy_nieterau@hotmail.com> |
||
|---|---|---|
| .. | ||
| integration | ||
| lib | ||
| resources | ||
| unit | ||
| __init__.py | ||
| conftest.py | ||
| README.md | ||
Automatic tests for OpenPype
Requirements:
Tests are recreating fresh DB for each run, so mongorestore, mongodump and mongoimport command line tools must be installed and on Path.
You can find intallers here: https://www.mongodb.com/docs/database-tools/installation/installation/
You can test that mongorestore is available by running this in console, or cmd:
mongorestore --version
Structure:
- integration - end to end tests, slow (see README.md in the integration folder for more info)
- openpype/modules/MODULE_NAME - structure follow directory structure in code base
- fixture - sample data
(MongoDB dumps, test files etc.) tests.py- single or more pytest files for MODULE_NAME
- fixture - sample data
- openpype/modules/MODULE_NAME - structure follow directory structure in code base
- unit - quick unit test
- MODULE_NAME
- fixture
tests.py
- MODULE_NAME
How to run:
- use Openpype command 'runtests' from command line (
.venvin ${OPENPYPE_ROOT} must be activated to use configured Python!) --python ${OPENPYPE_ROOT}/start.py runtests
By default, this command will run all tests in ${OPENPYPE_ROOT}/tests.
Specific location could be provided to this command as an argument, either as absolute path, or relative path to ${OPENPYPE_ROOT}.
(eg. python ${OPENPYPE_ROOT}/start.py start.py runtests ../tests/integration) will trigger only tests in integration folder.
See ${OPENPYPE_ROOT}/cli.py:runtests for other arguments.
Run in IDE:
If you prefer to run/debug single file directly in IDE of your choice, you might encounter issues with imports.
It would manifest like KeyError: 'OPENPYPE_DATABASE_NAME'. That means you are importing module that depends on OP to be running, eg. all expected variables are set.
In some cases your tests might be so localized, that you don't care about all env vars to be set properly. In that case you might add this dummy configuration BEFORE any imports in your test file
import os
os.environ["OPENPYPE_DEBUG"] = "1"
os.environ["OPENPYPE_MONGO"] = "mongodb://localhost:27017"
os.environ["OPENPYPE_DATABASE_NAME"] = "openpype"
os.environ["AVALON_DB"] = "avalon"
os.environ["AVALON_TIMEOUT"] = "3000"
os.environ["AVALON_ASSET"] = "Asset"
os.environ["AVALON_PROJECT"] = "test_project"
(AVALON_ASSET and AVALON_PROJECT values should exist in your environment)
This might be enough to run your test file separately. Do not commit this skeleton though. Use only when you know what you are doing!