Debug mode allows you to add or update screens. This is useful if a screen is missing or if you have an account with autonomous detection disabled. You can also add blank screens.
Using debug mode
Choose Record in the editor and a debug session will start, which streams your app and allows you to run tests and perform actions in realtime.
To add actions, choose one or more actions from the menu and select Play to perform them.
If the screen was captured a second too soon or if the object tree is partial, click the refresh icon at the bottom of the screen to reload it.
After you are done, edit your test name, add assertions, and save.
Change the names of the screens and give them a meaningful names so other testers can easily identify them. This makes authoring much easier.
If you want to update a missing screen, just add the screen but don't perform any actions. You can also just add a new screen in debug and rename it afterwards to override the changes.
If you want to add or update a screen or any action in the middle of the test, use the breakpoint to pause the test and transition to recording mode. Every action or screen will be added in realtime.
To cancel the breakpoint, click it.
If your flow is long or you know the resource ID/Text you want to add to your test, you can add a blank screen to directly pull in the specific screen you want.
Add a blank screen.
Add a tap on resource ID or Text to identify the screen you want to add.
Run the test.
21Labs will capture the viewport and object tree while the test is being run. If you still see a blank screen in the test view, refresh the browser window to update the view.