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

Nice-to-have: Automated stress-testing (low priority) #157

Open
davidjoffe opened this issue Nov 23, 2022 · 0 comments
Open

Nice-to-have: Automated stress-testing (low priority) #157

davidjoffe opened this issue Nov 23, 2022 · 0 comments

Comments

@davidjoffe
Copy link
Owner

davidjoffe commented Nov 23, 2022

Would be nice to be able to automate certain core actions to help stress-test the game and engine, e.g. mainly:

  • Game exit (so a script could repeatedly run it, run some stress-tests, close it, repeat for hours)
  • Starting and running game
  • Incrementing levels
  • Exit game
  • Things like currently-beta in-game fullscreen switching, e.g. run it hundreds or thousands of times
    This could help make sure the code is robust and cleaning up where/when it should be etc.
    But it's far from necessary at this point.
    Some of the code may overlap with the idea of possibly doing recording/playback of games.

A command line option could possibly enable stresstests e.g. then a shell script could have a simple loop of e.g.:
"./davegnukem --stresstest"
and/or "./davegnukem --stresstest -f"
so it could sit in a loop running the game, letting it load and auto-increment levels, stresstest things like fullscreen toggle, cleanup.

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

No branches or pull requests

1 participant