AI Prompt Guide for Testers: Module 1 – Getting Started & Prompt Engineering for Testers

Artificial Intelligence is rapidly transforming the way quality assurance is delivered. At Inspired Testing, we see AI not as a replacement for human judgment, but as a powerful accelerator of it. This guide has been designed for testers who are using general AI tools such as ChatGPT, Gemini, or Claude. Its purpose is to help you harness AI responsibly, effectively and in alignment with Inspired Testing’s values of technical excellence, integrity and quality.

Through structured prompts and practical examples, this guide will show you how to:

• Analyse requirements more thoroughly
• Generate comprehensive and risk-based test cases
• Produce cleaner automation code and data sets faster
• Communicate results and insights more clearly
• Maintain full compliance with ISO 27001 and ethical AI standards

Each module has been developed to mirror the way Inspired Testing consultants work combining deep testing expertise with practical efficiency. Every example prompt is designed to make AI collaboration part of your daily testing workflow, whether you’re working on web, mobile, performance, or enterprise systems.

Remember: AI is only as valuable as the precision and context of your prompts. The more specific, structured and ethical your inputs are, the better the outputs will be. Use this guide as both a training resource and a live reference in your projects.

Our goal: to enable every Inspired Testing professional to work smarter, faster and more effectively with AI as a trusted partner in quality.

 Module 1 – Getting Started & Prompt Engineering for Testers

1.1 The Role of AI in Testing

AI does not replace professional judgement. It enhances productivity by:

• Generating structured test ideas in seconds
• Supporting rapid analysis of ambiguous requirements
• Assisting with automation or defect documentation
• Producing summaries and stakeholder-ready explanations

AI accelerates your thinking it doesn’t replace it.

1.2 Responsible Use at Inspired Testing

All testers must comply with Inspired Testing’s ISO 27001 policy:

• Never paste client data, code, or credentials into public AI tools.
• Use synthetic or anonymised examples.
• Treat every AI output as a draft to be verified.
• Maintain human review and accountability for deliverables.

1.5 Prompting Techniques

A. Role-Based Prompting Example:

• You are a test lead at Inspired Testing reviewing user stories.
• Identify five ambiguities and suggest clarifying questions for the business analyst.

B. Context-Rich Prompting Example:

• You are validating the requirement:
• ‘System must support password resets via email.’
• List functional, negative and edge test scenarios.

C. Structured Output Prompting

Provide output as a Markdown table with columns:

Scenario ID | Input | Expected Result | Type (Positive/Negative)

D. Iterative Refinement

1.  Start broad → “List test cases for a login page.” 2. Narrow → “Now focus on session-handling negatives.” 3. Format → “Convert the final set to Gherkin scenarios.”

1.6 Advanced Prompt Patterns

Chain of Thought

You are a QA specialist preparing for exploratory testing.

Step 1 – Identify primary user actions. 

Step 2 – Derive test heuristics. 

Step 3 – List edge cases grouped by risk level.

Constraint-Driven

Generate exactly 8 test scenarios for an online checkout:

4 positive + 4 negative, each under 25 words.

Few-Shot

Provide an example → the AI learns your format:

Example:

| ID | Scenario | Expected |

|----|-----------|-----------|

| TC01 | Valid email & password | Redirect to dashboard |

Now create 10 more in the same format.

1.7 Refining AI Output

Use follow-up prompts to evolve results:

• “Expand this to include boundary cases.”
• “Focus on security testing aspects.”
• “Summarise for management audience.”
• “Add a column for test-data requirements.”

1.8 Inspired Testing QA Prompt Framework

ROLE: [QA lead | Test analyst | Automation engineer] 

CONTEXT: [Feature, API, requirement] 

TASK: [Generate test cases | Write defect | Summarise report] 

FORMAT: [Table | Gherkin | JSON | Summary] 

CONSTRAINTS: [# of items, tone, length, focus]

Example

ROLE: Senior QA consultant at Inspired Testing 

CONTEXT: Password-reset workflow for a banking app 

TASK: Create 12 functional and negative test scenarios 

FORMAT: Markdown table (ID, Scenario, Expected Result, Notes) 

CONSTRAINTS: One scenario per step; note dependencies

1.10 Do’s and Don’ts

✅ Do's:

• Use AI for brainstorming and drafting.
• Verify every output yourself.
• Use structured prompts for consistency.
• Combine AI and human analysis.

🚫 Don’t

• Paste client data or confidential artefacts.
• Assume AI answers are factually accurate.
• Request opinions on clients or people.
• Depend solely on AI judgement.

1.11 Example Workflow

Prompt 1: List functional and boundary test cases for registration form. 

Prompt 2: Add negative cases for missing mandatory fields. 

Prompt 3: Convert to Gherkin format. 

Prompt 4: Highlight top 3 high-risk scenarios.

1.12 Key Takeaways

• Clear intent + structure + iteration = useful results.
• Protect client data and confidentiality.
• AI enhances your testing intelligence — it doesn’t replace it.
• Review and refine everything you generate.

If you’d like to read the full article, you can view it on our website: https://www.inspiredtesting.com/news-insights/insights/692-ai-prompt-guide-for-testers