🏁Executing the Test

Important: Remember to save your test prompt frequently while editing. Exiting the test editor without saving will result in the loss of any recent changes.

Step 1: After completing the prompt editing, restart the emulator by clicking the Show restart options button and selecting Restart emulator. Wait or navigate within the app to reach the necessary state that corresponds to the screen indicated in the first step from which you want the execution to commence.

Step 2: Initiate the test execution by selecting Execute prompt to start GPT Driver.

Step 3: Allow GPT Driver to work its magic. The tool will analyze the screen with a 'Thinking...' text displayed and execute the relevant action command accordingly.

Step 4: While the steps are being executed, scroll down to the execution log to observe how GPT Driver is interacting with the app. Each interaction is represented by a yellow circle with a red dot in the middle. The execution log also provides details about the interaction and the reasoning behind it. This information becomes crucial if the expected behavior of GPT Driver deviates, prompting the need for editing the test prompt.

Step 5: Once GPT Driver has completed the steps, you will see either a "Succeeded" or "Failed" message along with a reason for the status. Feel free to review the execution logs to verify that the intended actions are occurring as expected.

Once your test has succeeded in the Test Editor a sufficient number of times (we recommend X5 as a minimum threshold), it's ready to be executed from the Test Overview. However, if the test prompt still encounters failures, consider further revision within the Test Editor to increase its accuracy.

Helpful Tips

  • Much like the Recorded Actions, you'll find the Execution Log now visible within the Prompt Editor. This log serves a comparable purpose, but with a detailed tracking of every interaction the GPT Driver has with the app, along with its underlying reasoning throughout the Test Prompt steps. Utilize the execution log to follow each step closely and pinpoint areas where enhancements to the prompt may be required

Anything unclear? Check out our FAQ section for additional guidance. Alternatively feel free to reach out to us directly via Slack or Email.

Last updated