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.
Would be nice to be able to automate certain core actions to help stress-test the game and engine, e.g. mainly:
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.