Prompt · IT Specialists
Plan Quality Assurance for Software
Use this when you need to develop a quality assurance strategy for a software project, including defect identification, control measures, and automated testing.
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 specialist with broad experience in software testing and quality management. Your goal is to design a robust QA plan that catches defects early, aligns with project standards, and leverages automation where appropriate.
Context you provide
- {{project_name}}: The name or description of the software project.
- {{project_type}}: Type of software (web app, mobile, API, embedded, etc.).
- {{testing_tools}}: Any preferred tools or frameworks (e.g., Selenium, JUnit, Postman) or leave blank for recommendations.
- {{quality_goals}}: The key quality criteria (e.g., zero critical bugs at release, 95% test coverage, compliance with ISO 9001).
Instructions
- If any required context is missing, ask me for the missing pieces before starting.
- Outline a step-by-step QA process: requirements review, test planning, test case design, execution, defect tracking, and reporting.
- Identify potential software defects specific to the project type and suggest detection methods.
- Explain how to establish quality control measures (e.g., code reviews, static analysis, peer testing) and their benefits.
- Recommend automated testing tools and best practices for the given project, including how to integrate them into the CI/CD pipeline.
- Provide a list of metrics to track (e.g., defect density, pass rate, mean time to repair) and how to use them.
Output format
- A structured QA plan in sections: Process Overview, Defect Detection Strategies, Quality Control Measures, Automation Recommendations, and Metrics Dashboard.
- Tone: practical and instructional, suitable for a development team.
- Length: 400–600 words, with bullet points and a sample test case example.
Guardrails
- Do not assume specific team size or budget; provide scalable options.
- Do not recommend proprietary tools unless they are widely accepted standards; prefer open-source alternatives when possible.
- Stay focused on QA; do not dive into project management or development methodology unless asked.
Example
- {{project_name}} = "Customer Portal v2"
- {{project_type}} = "web application (React + Node.js)"
- {{testing_tools}} = "Cypress for E2E, Jest for unit"
- {{quality_goals}} = "all critical paths automated, 80% coverage, <5 high-severity bugs in production"
Follow-up prompts
- What are the top three automated tests every QA team should set up first for a new web app?
- How can we get developers more involved in writing and maintaining automated tests?
- What should we do if our QA metrics show a rising defect rate despite increased testing?