{ "componentChunkName": "component---src-templates-page-jsx", "path": "/docs/test-management/qi-home/ad-hoc/write-effective-prompts/", "result": {"data":{"markdownRemark":{"html":"
\n

The quality of your prompt determines the quality of Atto's output.

\n
\n

Prompts are how you tell Atto what to test. A well-written prompt gives Atto the goal, the context, and the constraints it needs to generate test cases that are accurate and relevant. Vague prompts produce generic test cases. Specific prompts produce test cases that match your feature.

\n

This article covers how to write prompts that get you the right test cases the first time.

\n
\n
\n

Prerequisites

\n

Before you begin, ensure that:

\n\n
\n
\n

Where to Write Your Prompt

\n

The prompt input area is the large text field in the center of the Playground, below the heading What would you like to test?

\n\n

Type your prompt directly into this field. Attached context sources appear as badges above the input. Once your prompt is ready, click Generate with AI to start test case generation.

\n
\n

What Makes a Good Prompt

\n

Think of your prompt like a well-written test case title or a bug report. It needs to be clear, specific, and actionable. Vague prompts produce generic test cases. Specific prompts produce test cases that match your feature.

\n

Use the WHO + WHAT + WHY + HOW + EXAMPLES model to structure your prompt:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ElementDescriptionExample
WHOUser role or system under test\"As a registered user…\"
WHATFeature or action being tested\"…resetting a password…\"
WHYPurpose or expected behavior\"…to ensure expired tokens are handled.\"
HOWConstraints, variations, platforms\"Include 2FA and expired token scenarios.\"
EXAMPLESSeed inputs or expected outputs\"E.g., the token expires after 10 minutes.\"
\n

You do not need to use all five elements every time. Start with WHAT and add the others based on the complexity of the feature you are testing.

\n
\n

Prompt Checklist

\n

Before clicking Generate with AI, run through this checklist:

\n\n

If all four are covered, you are ready to generate.

\n
\n

Prompt Templates

\n

Use these templates as a starting point. Copy, edit, and paste into the Playground.

\n

Template 1: Feature Workflow

\n

Goal: Generate test cases for [feature or process].

\n

What I Have: [User roles or types] [Interaction methods or entry points] [Supporting features or integrations]

\n

What I Want: Cover [all combinations / edge cases / failure scenarios / retries]. Include [validation / exception handling / third-party behavior].

\n

Expected Outcomes: [Comprehensive coverage / error handling / reliability / user messaging]

\n

Example using this template:

\n

Goal: Generate test cases for an e-commerce checkout process.

\n

What I Have:

\n\n

What I Want:

\n\n

Expected Outcomes:

\n\n

Template 2: Transactional Feature

\n

Goal: Generate test cases for [banking or financial features].

\n

What I Have: [Transaction modes or account types] [User roles] [Limits, authentication methods, schedules]

\n

What I Want: Test all valid transaction paths. Include invalid inputs, failed authentication, and limit breaches. Check for audit trails and user notifications.

\n

Expected Outcomes: High-confidence coverage of transaction logic. Secure, validated, and compliant flows. Complete visibility into failures and success tracking.

\n

Example using this template:

\n

Goal: Generate test cases for the funds transfer feature in a banking app.

\n

What I Have:

\n\n

What I Want:

\n\n

Expected Outcomes:

\n\n

Template 3: Booking and Scheduling

\n

Goal: Generate test cases for [booking or scheduling feature].

\n

What I Have: [User types: guest, registered] [Booking types and variations] [Payment methods, policies, modification rules]

\n

What I Want: Test booking and modification flows across all types. Include failures in input validation, payment, and rescheduling logic. Cover scenarios around eligibility and penalties.

\n

Expected Outcomes: Full validation of booking and post-booking changes. Smooth error recovery for user actions and system failures. User clarity through pricing, penalties, and confirmation messages.

\n

Example using this template:

\n

Goal: Generate test cases for flight booking and rescheduling.

\n

What I Have:

\n\n

What I Want:

\n\n

Expected Outcomes:

\n\n
\n

Tips for Better Prompts

\n\n

When your prompt is ready, see Generate Test Cases.

\n
","frontmatter":{"title":"Write Effective Prompts","page_title":"Write Effective Prompts","metadesc":"The quality of your prompt determines the quality of Atto output. Learn how to write clear, specific prompts that generate accurate, relevant test cases.","noindex":false,"contextual_links":[{"type":"section","name":"Contents","url":null},{"type":"link","name":"Prerequisites","url":"#prerequisites"},{"type":"link","name":"Where to Write Your Prompt","url":"#where-to-write-your-prompt"},{"type":"link","name":"What Makes a Good Prompt","url":"#what-makes-a-good-prompt"},{"type":"link","name":"Prompt Checklist","url":"#prompt-checklist"},{"type":"link","name":"Prompt Templates","url":"#prompt-templates"},{"type":"link","name":"Tips for Better Prompts","url":"#tips-for-better-prompts"}]},"fields":{"slug":"/docs/test-management/qi-home/ad-hoc/write-effective-prompts/"}}},"pageContext":{"slug":"/docs/test-management/qi-home/ad-hoc/write-effective-prompts/","prev":{"fields":{"slug":"/docs/test-management/qi-home/ad-hoc/attach-context-sources/"},"frontmatter":{"title":"Attach Context Sources","metadesc":"Attach context sources such as Jira, Confluence, Figma, files, and video recordings so Atto generates test cases that accurately reflect your feature.","canonical":null,"keywords":null,"social_share_summary":null,"social_share_desc":null,"social_share_image":null,"noindex":false}},"next":{"fields":{"slug":"/docs/test-management/qi-home/ad-hoc/generate-test-cases/"},"frontmatter":{"title":"Generate Test Cases","metadesc":"Write your prompt, click Generate with AI, and Atto builds your test cases. Learn how to trigger Ad-Hoc generation and read the generation summary.","canonical":null,"keywords":null,"social_share_summary":null,"social_share_desc":null,"social_share_image":null,"noindex":false}}}}, "staticQueryHashes": ["2855385900","63159454"]}