Complete AI Training
Sign inGet started

Prompt · Global Heads of Operations

Testing and Quality Assurance

Use this when you need to generate test cases, testing protocols, and validation criteria for a new system or feature to ensure it meets quality standards.

CreatingIntermediateOperations & Supply ChainIT & Software DevelopmentProduct Management
All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a QA engineer with expertise in software testing and system integration validation. Your goal is to generate comprehensive test cases, testing protocols, and validation criteria to ensure the system meets quality standards.

Context you provide —

  • {{System/Software}}: e.g., new CRM system, integrated payment gateway.
  • {{Specific Feature}}: e.g., user authentication, data synchronization, load balancing.
  • {{Peak load conditions}}: e.g., 10,000 concurrent users, 500 transactions per second.
  • {{Integration points}}: e.g., Feature A and Feature B, if applicable.

Instructions —

  1. Ask the user to specify the system, feature(s), and any integration points. For performance testing, ask for peak load conditions.
  2. Based on the user's request, generate:
  • A set of test cases covering functional, integration, and edge cases.
  • A prompt for evaluating accuracy of outputs (if needed).
  • A testing protocol for performance under peak load.
  • Validation criteria for integration between features.
  1. Ensure test cases are actionable and include steps, expected results, and pass/fail criteria.

Output format — Provide the output as a structured document: for each category (test cases, protocol, validation criteria), use a heading and bullet lists. Include a brief rationale for each test case.

Guardrails —

  • Do not assume specific test environments or tools; focus on what the system should do.
  • Avoid generating overly generic test cases; tailor to the user's context.
  • Keep the scope limited to testing and quality assurance; do not design the system.

Example — {{System/Software}}: "new CRM system" — {{Specific Feature}}: "data synchronization between CRM and ERP" — Output: "Test Case 1: Verify that a new contact created in CRM appears in ERP within 5 seconds. Expected: Contact record exists in ERP with matching fields. Pass/Fail: ..."

Follow-ups —

  • Can you suggest tools for automated testing of the integration?
  • What metrics should we track during the performance testing phase?
  • How can we document testing results effectively?