In this guide, we will explain important concepts and useful prompt tips for using Autopilot effectively.
If you are new to Autopilot, please refer to the following pages:
MagicPod Autopilot Prompt Examples
Table of contents
- Start with small tasks
- Explain using common terminology
- Include rules in the prompt if there are any for test creation
- When test cases are not generated as expected
Start with small tasks
When you first use Autopilot, we recommend starting with small tasks and gradually increasing the complexity.
Small tasks mean giving specific instructions for areas where only a few steps need to be added or modified, and where there are no screen changes.
Benefits
- Easier to understand Autopilot's behavior
- Easier to find the cause when the results are not correct
- Easier to verify the quality of generated test cases
Prompt Examples
- If a pop-up ad appears after step 10, please modify the test to click the X button.
- In step 3, a new tab opened, but the screen did not change, and the test failed. Please fix it.
- Please modify the test so that it keeps clicking the "Update" button until it disappears.
- Please add a step to select "Tokyo" from the dropdown menu between step 3 and step 4.
Once you get used to Autopilot, you can gradually try more complex or abstract tasks.
Explain using common terminology
When requesting test generation from Autopilot, we recommend using common and general terminology.
Even though AI has wide knowledge, it may not understand company-specific terms, internal abbreviations, or unique naming. Using common wording helps Autopilot understand your meaning and create more accurate test cases.
Prompt Examples
-
Create a test for the one-click purchase feature
→ Create a test that clicks the "Buy Now" button and verifies the displayed amount
-
Verify the MUP value
→ Add a step to verify the value displayed in the "Monthly Active Users" label
Include rules in the prompt if there are any for test creation
If your project or team has rules or guidelines for test creation, specifying them in the prompt will help Autopilot generate more appropriate test cases.
By adding the rules in the prompt, test cases aligned with your team's policies will be automatically generated. This reduces the manual effort of post-editing and enables efficient test creation.
Rule Examples
- Naming conventions: Variable name formats, etc.
- Test data: Test accounts to use and prohibited items
- Comments: When to include comments, etc.
Prompt Examples
-
Create steps to complete member registration using the following information:
- Username: magicpod-user
- Email address: magicpod-user@example.com
- Create steps to log in by entering the username and password. The variable naming conventions are as follows:
- Use camelCase (e.g., userName, loginPassword)
- Use English naming, not Japanese
When test cases are not generated as expected
If the test generated by Autopilot does not work as expected, please communicate the problem specifically as follows.
Information to include in prompts
- Which step failed
- What error message appeared
- What is the state of the screen
- Any specific behavior causing the failure
Prompt Examples
- A timeout error occurs at step 15. Since the page takes time to load, please add a 5-second wait time
- A new tab opened at step 8, so elements cannot be found in subsequent steps. Please add a step to switch tabs