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.

|test-case-generation.md

Generate test cases for: [Feature Name]

Requirements:
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

Include:
- Positive test cases (happy path)
- Negative test cases (error handling)
- Edge cases and boundary conditions
- Performance considerations

Format: Given-When-Then

Customization 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.

|bug-report.md

Enhance this bug report:

What happened: [Your brief description]

Expected result: [What should happen]

Actual result: [What actually happened]

Make it:
- Clear and concise
- Include reproduction steps
- Suggest severity level
- Add relevant technical details

3. API Test Scenarios

Use when: Testing REST APIs and need comprehensive scenario coverage.

|api-testing.md

Generate API test scenarios for:

Endpoint: POST /api/users
Request body: { "email": "...", "name": "...", "role": "..." }

Consider:
- Valid/invalid authentication
- Missing/extra fields
- Data type validation
- Rate limiting
- Idempotency
- Status codes

Pair 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.

|user-journey.md

Map user journeys for: [Feature/Product]

User persona: [Target user type]

Starting point: [Where user begins]
Goal: [What user wants to achieve]

Create 3 journey maps:
1. Ideal path (no errors)
2. Common obstacles path
3. Edge case path

Include decision points and potential failures.

5. Security Testing Checklist

Use when: Preparing security-focused test cases.

|security-checklist.md

Generate security testing checklist for: [Feature]

Focus areas:
- Input validation
- Authentication/Authorization
- Data encryption
- SQL injection
- XSS vulnerabilities
- CSRF protection
- Session management

Prioritize 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.

|regression-prioritization.md

Prioritize these test cases for regression:

[List your test cases]

Criteria:
- Feature criticality
- Recent code changes
- Historical defect density
- Business impact

Suggest: High/Medium/Low priority with reasoning.

7. Test Data Generation

Use when: Need realistic test data that covers edge cases.

|test-data.js

// Prompt for test data
Generate test data for user registration:

Fields:
- Email (valid/invalid formats)
- Password (strong/weak/edge cases)
- Age (valid range: 18-120)
- Phone number (US format)

Include:
- 5 valid sets
- 10 invalid sets (with reasons)
- 5 edge case sets

8. Performance Test Scenarios

Use when: Planning performance testing.

|performance-scenarios.md

Design performance test scenarios for: [Feature]

Expected load:
- Average users: [number]
- Peak users: [number]
- Response time target: [ms]

Generate scenarios for:
- Load testing
- Stress testing
- Spike testing
- Endurance testing

9. Accessibility Testing Guide

Use when: Need to verify accessibility compliance.

|accessibility-testing.md

Generate accessibility testing guide for: [Feature/Page]

WCAG Level: AA

Check:
- Keyboard navigation
- Screen reader compatibility
- Color contrast
- Focus indicators
- ARIA labels
- Alternative text

Provide 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.

|exploratory-charter.md

Create exploratory testing charter:

Feature: [Feature name]
Time box: [Duration]
Focus: [What to explore]

Suggest:
- 5 areas to explore
- Potential risk areas
- Questions to answer
- Heuristics to apply

How 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.