ayon-core/tests
2022-04-06 14:15:38 +02:00
..
integration Fix - moved conftest to be applicable for all kind of tests 2022-04-06 14:15:38 +02:00
lib Added timeout to command line arguments 2022-02-16 18:08:15 +01:00
resources #1784 - added howto create new publishing test 2021-09-06 18:42:34 +02:00
unit OP-2813 - changed logic of parsing frames from names 2022-03-18 11:13:10 +01:00
__init__.py #1784 - added base implementation for helper DB class 2021-07-07 18:51:55 +02:00
conftest.py Fix - moved conftest to be applicable for all kind of tests 2022-04-06 14:15:38 +02:00
README.md OP-2813 - fix typo 2022-03-18 12:27:15 +01:00

Automatic tests for OpenPype

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
  • unit - quick unit test
    • MODULE_NAME
      • fixture
      • tests.py

How to run:

  • use Openpype command 'runtests' from command line (.venv in ${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["AVALON_MONGO"] = "mongodb://localhost:27017"
os.environ["OPENPYPE_MONGO"] = "mongodb://localhost:27017"
os.environ["AVALON_DB"] = "avalon"
os.environ["OPENPYPE_DATABASE_NAME"] = "openpype"
os.environ["AVALON_TIMEOUT"] = '3000'
os.environ["OPENPYPE_DEBUG"] = "3"
os.environ["AVALON_CONFIG"] = "pype"
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!