We used this in a videogame engine test framework to verify specific game states against gold-master images. It was particularly useful for verifying when our physics engine had changed in subtle ways; one of our tests involved dropping a couple of boxes on top of each other and verifying where they landed.
All kinds of stuff would disrupt that test---which made it great for knowing when we'd changed something subtle that would have real impact on our game engine's users.
Comments
http://www.sikuli.org/
We used this in a videogame engine test framework to verify specific game states against gold-master images. It was particularly useful for verifying when our physics engine had changed in subtle ways; one of our tests involved dropping a couple of boxes on top of each other and verifying where they landed.
All kinds of stuff would disrupt that test---which made it great for knowing when we'd changed something subtle that would have real impact on our game engine's users.
Yeah, this is complicated, it may have changed but it may still be correct
like a value of 15.000002 instead of 15.000013 but errors may accumulate in the end.
Yeah, I love Sikuli. I've only used it to automate clicking through game GUI, not for anything in the game scene itself.