(11-11-2009, 12:47 PM)cruonit Wrote: When someone changes the code some games can get broken (whats happening from release to release).
In order to get feedback what is broken/what games that previously worked the developers need feedback from the community (testers).
I am suggesting a more sistematical method how to semiauto(or auto) test if some games got broken after a release.
let's say mario worked on release 4460 with some options enabled so we have a saved picture at time 0:20 after the game was launched(let's say its the menu of the game)
but let's say on release 4525 the game is broken and at 0:20 after the game was lounched automatically by the testing application we only see a black screen or some textures are missing.
It's hard to write unit tests to test this by coding. It's easier to detect it visually by comparing two screenshots in this example one archived from the release 4460 and the other generated by the testing application from the 4525 release.
So the testers only need to compare screenshots to see if a game is broken and such compares can be done quickly.
Maybe this wouldn't be useful for the developers but the community will be able to see how the game worked in different releases (they could also see the FPS from the screenshots)
I agree it would be GREAT to have something like this, someone just has to do it
What's needed is to have to little hooks in dolphin to make it auto-screenshot at frame number 200 (for example) and exit or load the next game, etc, and then make a program or script to drive it all.The only problem is that anyone who'd like to run it needs to have all or at least many of the games being tested.