10 ChatGPT Prompts Every QA Should Have in Their Toolkit
After months of experimenting with AI in testing, I've compiled my most-used ChatGPT prompts. These are the ones I reach for daily—the ones that actually save time and improve quality.
New to AI in testing? Start with prompts #1 and #2. They're the easiest to adapt and deliver immediate value.
1. Test Case Generation
Use when: You have clear requirements and need comprehensive test coverage.
1Generate test cases for: [Feature Name]
2
3Requirements:
4- [Requirement 1]
5- [Requirement 2]
6- [Requirement 3]
7
8Include:
9- Positive test cases (happy path)
10- Negative test cases (error handling)
11- Edge cases and boundary conditions
12- Performance considerations
13
14Format: Given-When-ThenCustomization tip: Add your team's specific test case format or template.
2. Bug Report Enhancement
Use when: You've found a bug but struggle to describe it clearly.
1Enhance this bug report:
2
3What happened: [Your brief description]
4
5Expected result: [What should happen]
6
7Actual result: [What actually happened]
8
9Make it:
10- Clear and concise
11- Include reproduction steps
12- Suggest severity level
13- Add relevant technical details3. API Test Scenarios
Use when: Testing REST APIs and need comprehensive scenario coverage.
1Generate API test scenarios for:
2
3Endpoint: POST /api/users
4Request body: { "email": "...", "name": "...", "role": "..." }
5
6Consider:
7- Valid/invalid authentication
8- Missing/extra fields
9- Data type validation
10- Rate limiting
11- Idempotency
12- Status codesPair this with tools like Postman or REST Client. Generate scenarios with AI, then automate them with your preferred tool.
4. User Journey Mapping
Use when: Need to map out complex user workflows for testing.
1Map user journeys for: [Feature/Product]
2
3User persona: [Target user type]
4
5Starting point: [Where user begins]
6Goal: [What user wants to achieve]
7
8Create 3 journey maps:
91. Ideal path (no errors)
102. Common obstacles path
113. Edge case path
12
13Include decision points and potential failures.5. Security Testing Checklist
Use when: Preparing security-focused test cases.
1Generate security testing checklist for: [Feature]
2
3Focus areas:
4- Input validation
5- Authentication/Authorization
6- Data encryption
7- SQL injection
8- XSS vulnerabilities
9- CSRF protection
10- Session management
11
12Prioritize by risk level.Security testing is critical. Use AI to generate the checklist, but always have security experts review sensitive areas.
6. Regression Test Prioritization
Use when: Limited time for regression testing.
1Prioritize these test cases for regression:
2
3[List your test cases]
4
5Criteria:
6- Feature criticality
7- Recent code changes
8- Historical defect density
9- Business impact
10
11Suggest: High/Medium/Low priority with reasoning.7. Test Data Generation
Use when: Need realistic test data that covers edge cases.
1// Prompt for test data
2Generate test data for user registration:
3
4Fields:
5- Email (valid/invalid formats)
6- Password (strong/weak/edge cases)
7- Age (valid range: 18-120)
8- Phone number (US format)
9
10Include:
11- 5 valid sets
12- 10 invalid sets (with reasons)
13- 5 edge case sets8. Performance Test Scenarios
Use when: Planning performance testing.
1Design performance test scenarios for: [Feature]
2
3Expected load:
4- Average users: [number]
5- Peak users: [number]
6- Response time target: [ms]
7
8Generate scenarios for:
9- Load testing
10- Stress testing
11- Spike testing
12- Endurance testing9. Accessibility Testing Guide
Use when: Need to verify accessibility compliance.
1Generate accessibility testing guide for: [Feature/Page]
2
3WCAG Level: AA
4
5Check:
6- Keyboard navigation
7- Screen reader compatibility
8- Color contrast
9- Focus indicators
10- ARIA labels
11- Alternative text
12
13Provide specific test steps.Accessibility matters. Use tools like axe DevTools or WAVE alongside these test cases for comprehensive coverage.
10. Exploratory Testing Charter
Use when: Starting an exploratory testing session.
1Create exploratory testing charter:
2
3Feature: [Feature name]
4Time box: [Duration]
5Focus: [What to explore]
6
7Suggest:
8- 5 areas to explore
9- Potential risk areas
10- Questions to answer
11- Heuristics to applyHow to Use These Effectively
- Customize for your context: Add your specific business rules, compliance requirements, and domain knowledge
- Iterate: If the first output isn't great, refine your prompt
- Build a library: Save your best variations in a team wiki or Notion
- Combine prompts: Chain multiple prompts together for complex scenarios
Pro tip: Create a "prompt template" document with placeholders. Just fill in the blanks instead of writing from scratch each time.
Measuring Success
Track these metrics to see if AI prompts are helping:
- Time saved per test case (before vs after)
- Edge case coverage (number of edge cases caught)
- Bug detection rate (bugs found in testing vs production)
- Documentation quality (team feedback)
What's Next?
These prompts are a starting point. The real power comes from customizing them for your:
- Domain (e-commerce, healthcare, fintech, etc.)
- Technology stack (web, mobile, API, etc.)
- Team workflow (agile, waterfall, DevOps)
- Testing tools (Selenium, Cypress, JMeter, etc.)
Want more AI testing tips? Subscribe to my newsletter for weekly prompts, case studies, and practical workflows. No fluff—just actionable insights you can use Monday morning.