You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create additional screenshot tests and add an auto message on screenshot test failure
This adds screenshot tests for:
TestIssue2076
TestMotionPath
TestSimpleBumps
This also:
Automatically posts a comment if a screenshot test fails to help inform users what to do
The purpose of these tests is to ensure that changes introduced in this PR don't break visual features. They are visual unit tests.
99
+
100
+
📄 **Where to find the report:**
101
+
- Go to the (failed run) > Summary > Artifacts > screenshot-test-report
102
+
- Download the zip and open jme3-screenshot-tests/build/reports/ScreenshotDiffReport.html
103
+
104
+
⚠️ **If you didn't expect to change anything visual:**
105
+
Fix your changes so the screenshot tests pass.
106
+
107
+
✅ **If you did mean to change things:**
108
+
Review the replacement images in jme3-screenshot-tests/build/changed-images to make sure they really are improvements and then replace and commit the replacement images at jme3-screenshot-tests/src/test/resources.
109
+
110
+
✨ **If you are creating entirely new tests:**
111
+
Find the new images in jme3-screenshot-tests/build/changed-images and commit the new images at jme3-screenshot-tests/src/test/resources.
112
+
113
+
**Note;** it is very important that the committed reference images are created on the build pipeline, locally created images are not reliable. Similarly tests will fail locally but you can look at the report to check they are "visually similar".
114
+
115
+
See https://github.com/jMonkeyEngine/jmonkeyengine/blob/master/jme3-screenshot-tests/README.md for more information
0 commit comments