Games
Plays your game like a player, reads it like a developer.
Ordinary testing tools only see pixels on a game screen. TestSafe recognises every object inside the game by name. It gets past the menu, plays the level and finds the bug.
Examples
What does the agent do in a game?
In each example the instruction is on the left and what happened on the device is on the right.
- 01
Finishes the level before the moves run out
In a match game the agent reads the board, picks the move that serves the goal and tries to finish the level before the moves run out. If a goal counter is wrong or the blasts get stuck, it brings you that moment on video.
AI Instructions
AI
PROMPT
Finish level 42 before the moves run outFLOW PORTS
SuccessError - 02
Takes the shot itself and brings the tower down
The agent pulls the sling back, picks the angle and the power and takes the shot. If the tower is still standing it changes the angle on the next one. If a block hangs in the air or the score counts wrong, it brings you that frame on video.
AI Instructions
AI
PROMPT
Bring the whole tower down in three shotsFLOW PORTS
SuccessError - 03
Opens the store and reads the packs and prices
The agent opens the in-game store, reads every pack and looks at the price labels. If a price does not fit its box, a pack looks wrong or the store never opens, it brings you that frame on video.
AI Instructions
AI
PROMPT
Open the store and check the packs and pricesFLOW PORTS
SuccessError
For games
The agent reads your game from the inside.
An ordinary testing tool sees nothing but coloured pixels on a game screen. TestSafe reads the list inside the running game. Where the score label is, which button can be tapped, whether the character is on the field, whether an enemy left the screen. The list on the right is what the agent sees right now, and the phone shows where each one sits.
- Recognises the game's menus, buttons and characters
- It tests the exact version your players get
- The agent taps the button or object itself, not a spot on the screen
What the agent sees
Hover a row in the list and its box lights up on the phone.
Measured on every version
If the game got heavier, the numbers say so.
- FPS
- frame rate and stutters, level by level
- Memory
- memory and processor use, version to version
- Crashes
- crashes and freezes, with the video
Which games does it work with?
Mobile games that run on Android. The agent reads the inside of the game. It knows its menus, buttons and characters. Nothing is installed into the game, and the version your players get is the one that gets tested.
The player's phone
What happens when the battery dies mid-level?
Most of your players open the game on the metro, with the battery running out and notifications coming in. While the agent plays the level, you change the state of the phone and watch what the game does.
See device conditions →- The battery drops to 5 percent mid-level and the system warning covers the screen
- The network slows down or drops, and you see whether progress is saved
- A call comes in, and you see whether the game picks up where it left off
- The phone starts in another language, and you see whether the text still fits
Every release
When an update goes out, the same levels are played again
- 01
A new release
When a release is published on GitHub, the tests start with the new build.
- 02
While nobody is watching
Line your scenarios up as a workflow and they run one after another while nobody is watching.
- 03
Results to the team
The report arrives with its video in GitHub, Slack or Jira.
Let the agents play your game.
Book a demo and we'll watch a live run on your own game together.