Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a screenshot based set of tests for jMonkeyEngine #2279

Open
richardTingle opened this issue Jun 7, 2024 · 3 comments · May be fixed by #2280
Open

Create a screenshot based set of tests for jMonkeyEngine #2279

richardTingle opened this issue Jun 7, 2024 · 3 comments · May be fixed by #2280
Assignees

Comments

@richardTingle
Copy link
Member

richardTingle commented Jun 7, 2024

As discussed at https://hub.jmonkeyengine.org/t/screenshot-based-jme-testing/47685/18 I will be creating a set of automated tests that can run as part of the build on standardised hardware. The purpose of this is to reduce the amount of human testing required to assure ourselves that a new JME version has not broken some graphics based behaviour (which is difficult to test under normal automated testing)

Objectives:

  • Human readable html report including before and after screenshots for manual review
  • Diff screenshot showing where in the image there is a change
  • Easy (documented) mechanism for accepting changes
  • Failed pipeline on test fail
  • Ability for some tests to be marked as "non deterministic" and only triggering manual human review, not a failed test
  • Ability for some tests to be marked as "known broken" and only triggering manual human review, not a failed test
@richardTingle
Copy link
Member Author

(I don't think I have rights to assign myself to this issue, but for the avoidance of doubt I'm working on this)

richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 7, 2024
@MeFisto94
Copy link
Member

It seems you already worked on that, but just a heads up that I did so, too, a few years ago.
It could even run in docker using some CPU pipeline:
https://github.com/MeFisto94/jme3-testing

richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 8, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
…ease. Also rearrange tests to have a base class
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
@richardTingle richardTingle linked a pull request Jun 9, 2024 that will close this issue
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Jun 9, 2024
… equality (now that pipeline runs works again)
@richardTingle
Copy link
Member Author

@MeFisto94 Thank you for sharing that, thats interesting. Anything you think I need to watch out for from your previous experience? Did your docker version use cpu openGL rendering as well?

richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Nov 3, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Nov 3, 2024
richardTingle added a commit to richardTingle/jmonkeyengine that referenced this issue Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants