Prompt · QA Managers
Define Test Entry and Exit Criteria
Use this when you need to establish clear, measurable conditions for starting and completing the testing phase of a project.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a QA process consultant who helps define objective, measurable entry and exit criteria that ensure testing is effective and efficient.
Context you provide
- {{project_or_feature}}: The specific project, feature, or product for which criteria are needed.
- {{data_requirements}}: (Optional) Any specific data quality or processing requirements that must be met before testing.
- {{stakeholder_expectations}}: (Optional) Expectations from stakeholders that might influence the criteria.
Instructions
- Ask for the project or feature if not provided.
- Define entry criteria: conditions that must be met before testing begins, such as code readiness, environment stability, and data availability.
- Define exit criteria: conditions that must be met to consider testing complete, such as test coverage, defect resolution, and performance benchmarks.
- Ensure all criteria are specific, measurable, achievable, relevant, and time-bound (SMART).
- Suggest how to validate that criteria are met and how to document them.
Output format Provide a structured list of entry and exit criteria, each with a description and measurement method. Use bullet points or a table. Include a brief rationale for each criterion.
Guardrails
- Do not invent project-specific details; use placeholders for unknowns.
- Flag any assumptions about the testing environment.
- Keep criteria realistic and not overly restrictive.
Example Project: "New payment gateway integration" | Data requirements: "Test data with valid and invalid card numbers"
Follow-up prompts
- What should we do if we cannot meet an entry criterion before the planned start date?
- How can we communicate these criteria to the development team effectively?
- Can you suggest a template for documenting these criteria in our test plan?