Nuke testing class #2364
Merged
Nuke testing class #2364
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Used to differentiate between regular REMOTE_PUBLISH and automatic tests
Necessary env vars should be configured in testing zip file
It was overwriting existing value of NUKE_PATH before
Zip files now stored on OP shared GDrive PS implementation is not working, fixed in OP-2019
Belongs to merged PR for AE testing
|
Task linked: OP-2019 Create test publish class for AE |
|
Task linked: OP-2042 nuke testing class |
![hound[bot]](https://avatars.githubusercontent.com/in/3598?s=60&v=4){kind=small}
|
All issues after review implemented. Mentioned |
…sible For better automatic testing
| @@ -100,6 +108,14 @@ def env_var(self, monkeypatch_session, download_test_data): | |||
| import openpype | |||
|
|
|||
| openpype_root = os.path.dirname(os.path.dirname(openpype.__file__)) | |||
|
|
|||
| #reset connection to openpype DB with new env var | |||
It tells Nuke where it should locate test input data
Paths in write nodes could contain python code for automatic testing. It needs to be evaluated to all os operations to work properly.
Explicitly sets directory of published files. (Purges them if exist!)
Added DBAssert class which wraps standard use cases for asserts
| monkeypatch_session.setenv("NUKE_PATH", | ||
| "{}{}{}".format(startup_path, | ||
| os.pathsep, | ||
| original_nuke_path)) |
| @@ -0,0 +1,45 @@ | |||
| """Classed and methods for comparing expected and published items in DBs""" | |||
|
|
|||
| class DBAssert: | |||
| @pytest.fixture(scope="module") | ||
| def startup_scripts(self, monkeypatch_session, download_test_data): | ||
| """"Adds init scripts (like userSetup) to expected location""" | ||
| raise NotImplementedError |
|
Added bunch of updates:
|
64qam
approved these changes
Dec 13, 2021
|
All other features will be implemented in next PRs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implemented pytest testing class for Nuke.
Pulls prepared testing zip file from GDrive, prepares temporal DBs(avalon, openpype), opens Nuke, publishes basic workfile, compares result.
(in activated {OPENPYPE_ROOT}/.venv)
{OPENPYPE_ROOT}/.venv/Scripts/python.exe {OPENPYPE_ROOT}/start.py runtests {OPENPYPE_ROOT}/tests/integration/hosts/nuke(Contains merged PR for OP-2019- ynput/avalon-core#391)(Contains commit with current avalon-core)