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.
I'm a paragraph. Click here to add your own text and edit me. It's easy.