I've setup a first pass of automated UI testing in AeroCEO.
Earlier, I had already separated the GUI code into it's own library, this way I could have it loaded into a normal executable for releasing the game. But also in an second executable along with the server code for easily development and testing without having to run a server separately. Now I can load this GUI within a third executable, within a testing framework that can push buttons and speed through time to allow for writing tests.
I've just got a simple proof of concept for now, where the game will wait until the splash screen disappears and the main menu is available, then clicks the start game button, then confirms that it is now in the game proper.
In the future we'll be able to do lots of tests to check every screen and menu to make sure the game is solid and bug free as I improve and extend it.
Previous: UI Dock