Added test tool to do UI snapshot testing #343
Closed
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.
DRAFT PR UNTIL BUILD WORKFLOW IS UPDATED TO UPLOAD SCREENSHOTS OF FAILED TESTS
Summary
To prevent issues like #312 from reoccurring I added a one-line tool that can be added to do snapshot testing similar to Jest.
When initially hit, Unity creates a screenshot, which needs to be committed to the repository. For all subsequent runs, Unity creates another screenshot and compares it with the one stored inside the repository.
Before/after screenshots and/or animated gif
Adding
yield return ScreenshotDiff.TakeScreenshotOrCompare()
to any test causes one these things to happen:/Assets/Tests/PlayModeTests/Tools/Screenshots/{FullNameOfTest}/{TakeScreenshotOrCompareWasCalledInsideTest}.png
/TestRunArtifacts/TestContext.CurrentTestExecutionContext.StartTime/{FullNameOfTest}.{TakeScreenshotOrCompareWasCalledInsideTest}
Testing instructions
not yet available
Additional information
[ ]
Changes UI[ ]
Introduces new feature[ ]
Removes existing feature[ ]
Has associated resource: