Write prompts
Describe the flow in plain English and Pie turns it into a test case. Walk through it the way you’d brief a teammate, and every action you mention becomes a step.
Pie follows a prompt more closely when it covers the whole workflow. These habits help most when you need precise control over one user path.
Before you start
- Pick a flow to test, and note the screens and data it touches.
- Choose where to enter the prompt: Chat, Pie Canvas or your agent. Create and edit test cases covers each route.
Spell out every action
Say where Pie should navigate, what it should click and what data it should enter. Mention the screen, the button, the fields to fill and how to save.
“Go to Settings > User Management. Click Add User, enter a unique email address, select the Admin role from the dropdown, and click Save.”
Include as much detail as you need. Every action you mention becomes a step in your test case.
Make values unique
To get fresh data on every run, add a note at the end of your prompt:
Note: To make the values unique, use the current date-timestamp{DDMMhhmmss}When you ask for a “unique name” or “unique email”, Pie appends a timestamp automatically. Each run then creates independent data with no collisions.
Use clear navigation paths
Use the > symbol to show the menu path:
Settings > Account > SecurityDashboard > Reports > MonthlyAdmin > Users > RolesShop > Categories > Electronics
Say where the navigation starts, such as the sidebar or a specific menu. Specific paths make the test more reliable.
“From the sidebar, navigate to Admin > Users > Roles. Select the Editor role, enable ‘Can Publish’ permission, and save.”
Search before you act
When a test creates a record and uses it later, add a search step so Pie works on the exact record it created. This matters most in environments with a lot of data.
“Go to Products > Catalog. Click Add Product, enter a unique product name, set price to 25.00, and save. Search for the newly created product, open it, change the price to 30.00, and save.”
End with a clear check
Finish with what should be true when the flow ends, such as “Verify the dashboard loads” or “Verify the page appears in the Published list”.
Examples
Each example combines these habits.
Signup and login flow
“Navigate to the Register page. Enter a unique email address, create a password with ‘Test123!’, accept the terms, and click Sign Up. Log out. Return to the Login page, enter the same email and password, and sign in. Verify the dashboard loads.”
Content management
“Go to Admin > Content > Pages. Click Create Page, enter a unique page title, add body text ‘Test content for validation’, set status to Draft, and save. Search for the newly created page, open it, change status to Published, and save. Verify the page appears in the Published list.”
E-commerce checkout
“Navigate to Shop > Products. Add the first available item to cart. Go to Cart, increase quantity to 2, verify the total updates. Click Checkout, enter a unique email and shipping address, select Express Shipping, and complete purchase with test card 4111111111111111.”
Settings validation
“Navigate to Settings > Notifications. Disable all email notifications and save. Refresh the page. Verify all email notifications remain disabled. Re-enable ‘Order Updates’ only and save.”
Record deletion
“Navigate to Contacts > All Contacts. Click Add Contact, enter a unique name and email, and save. Search for the newly created contact, select it, and click Delete. Confirm the deletion. Search for the same contact again and verify no results are found.”
Check your prompt before you submit
- Every action is spelled out in sequence.
- Navigation paths use the
>format. - A unique identifier note is included when the test creates records.
- A search step comes before any interaction with a created record.
- The prompt ends with a clear check.
What you’ll see
Pie turns the prompt into a test case with one step per action you described and the checks you asked for. Open it in Test Cases to read the steps, and edit any that are off.