Test scripts are written within a standard Integrated Development Environment. In this example, the test is constructed within Visual Studio using the C# API.
GameDriver's API works against the game engine's native objects, giving you unprecedented external control and access to the game's inner workings.
Once ready, test assets are compiled and the game is started. GameDriver's technology hooks itself onto in-game objects, giving the tests script complete control over the game state.
Tests can be run from the IDE, or as part of a continuous integration (CI/CD) pipeline.
Once completed, testers and developers can view whether each test passed or failed and determine how to resolve any regressions.
Unlike with manual testing, GameDriver tests are consistent and repeatable, significantly reducing user error from testing and shrinking defect resolution cycles.
March 26, 2019
Ok, so we've talked about the state of the industry and why games need test automation. We talked about open betas, and the risk they impose to your game development project. We talked about game monetization and how it is key to the long term success of a game. But we...
Please Stand By