fix: Unit test fix when DEADLINE_ENABLE_DEVELOPER_OPTIONS is True #40
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.
What was the problem/requirement? (What/Why)
The
test_initialize_and_uninitialize_plugin
unit test would fail if DEADLINE_ENABLE_DEVELOPER_OPTIONS was set to True:Error:
RegisterCommad is called twice if DEADLINE_ENABLE_DEVELOPER_OPTIONS is set to True: https://github.com/casillas2/deadline-cloud-for-maya/blob/mainline/maya_submitter_plugin/plug-ins/DeadlineCloudForMaya.py#L71
What was the solution? (How)
Set DEADLINE_ENABLE_DEVELOPER_OPTIONS to False when running unit test
What is the impact of this change?
Tests pass when DEADLINE_ENABLE_DEVELOPER_OPTIONS is set to True in shell environment
How was this change tested?
Ran unit tests locally
Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
N/A to change. Tests pass
Was this change documented?
No
Is this a breaking change?
No