Android screenshot tests#2809
Conversation
…a issues in screenshots
…ility in the pipelines
…t-tests-2 # Conflicts: # gradle/libs.versions.toml # settings.gradle
|
🖼️ Screenshot tests have failed. The purpose of these tests is to ensure that changes introduced in this PR don't break visual features. They are visual unit tests. 📄 Where to find the report:
✅ If you did mean to change things: ✨ If you are creating entirely new tests: 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". See https://github.com/jMonkeyEngine/jmonkeyengine/blob/master/jme3-screenshot-tests/README.md for more information Contact @richardTingle (aka richtea) for guidance if required |
…t-tests-2 # Conflicts: # gradle/libs.versions.toml # jme3-screenshot-tests/build.gradle # settings.gradle
1 participant
Allow a subset of the screenshot tests to be run on Android (a subset because some are too heavy and cause out of memory errors on the emulated android)
Extent reports doesn't work on Android so creates a proto report within android and later upgrades that to a proper report within the pipeline