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.

Sign up for GitHub

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

Jump to bottom

Create and run smoke tests after a build is complete #109

Open

PanosK92 opened this issue Sep 6, 2023 · 1 comment

Labels

doable from a contributor (medium) new feature

Owner

PanosK92 commented Sep 6, 2023

Create automated tests like so: https://twitter.com/i/status/1595058457471770628

This will reduce the probability of new changes breaking things, and the issues going unnoticed until someone stumbles upon them.

PanosK92 added new feature doable from a contributor (easy) labels

munnsmunns mentioned this issue

DRAFT: Add smoke tests #118

Closed

PanosK92 added doable from a contributor (medium) and removed doable from a contributor (easy) labels

Owner Author

PanosK92 commented Apr 4, 2024

The GitHub workflow has been updated to run the engine (after building it), it does so with the -ci_test argument.

If the renderer produces one frame, ci_test.txt will created (with a value of 0), which the workflow will then read to determine success.

This opens the path for any kind of smoke test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment