✍️Creating Tests Using Natural Language (AI) instructions
GPT Driver’s Prompt Assistant simplifies prompt writing by recording and transcribing device interactions into ready-to-use test prompts.
Last updated
GPT Driver User Guide
GPT Driver’s Prompt Assistant simplifies prompt writing by recording and transcribing device interactions into ready-to-use test prompts.
Last updated
To get started with creating tests using natural language (AI), check out this Quick Start (2 min): Video walkthrough of the Basics or read more below.
For more information and to avoid surprises, review the complete overview of supported AI instructions.
Natural and Freestyle Approach
Embraces a natural writing style for prompt creation
Clear, Numbered Steps
Breaks down prompts into easily digestible, numbered steps
Final Success Assertion
Upon reaching the test flow's endpoint, the Prompt Assistant generates a conclusive step. This final step includes a success assertion to verify the correct screen, ensuring test success before concluding.
Recorded Actions
Every screen interaction is captured with a screenshot, accompanied by an icon pinpointing the exact location of the interaction. This detailed recording is conveniently displayed below the Prompt box for your reference.
Step 1: Click on Tap to Play to initiate the emulator. Rename the test case by choosing Untiled and entering your preferred test case name. Let's designate this test case as 'Test.'
Step 2: With the emulator initiated and the test renamed, proceed to the Assistant tab.
Step 3: In the Assistant tab, choose the Record interactions with the app button.
Step 4: At this point, every interaction, such as tapping on elements or typing, will be recorded. Please allow some time for the steps to be generated. In this example, simply tap on the 'Get Started' button.
Step 5: In this example, our desired test case involves selecting the 'Get Started' button and landing on a screen with the text 'Explore quick & easy recipes you will love.' Since this constitutes the entire test case, we can now stop the recording. Upon stopping, you will be prompted to Add a success assertion, which we highly recommend. If you consider this to be the final screen for the test case, choose Yes. If you prefer to temporarily pause the interaction recording with the app, select No, thanks. Please be patient while the test assertion step is being generated. We are finished for this section!
Tap directly on text elements if available to avoid generating coordinates.
Avoid tapping on or referencing dynamic elements, buttons or content.
After recording a click journey, transfer the recorded actions to the test editor. Review them to determine if additional assertions are required, e.g. for handling loading times or addressing optional screens.
If you need to pause the Prompt Assistant, press the stop button again and decline the Success Assertion to temporarily halt the recording. Ensure to return the app to the correct screen when resuming the recording.
Remember to save your test prompt frequently while editing. Exiting the test editor without saving will result in the loss of any recent changes.
