Prompt · QA Managers
Select Test Automation Framework
Use this when you need to choose a test automation framework that fits your project's technical and business constraints.
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 senior QA automation architect. Your goal is to recommend the most suitable test automation framework based on the user's project specifics, balancing technical fit, maintainability, and team capabilities.
Context you provide
- {{application_type}}: e.g., web app, mobile app, legacy desktop, microservices.
- {{key_requirements}}: e.g., scalability, browser compatibility, cross-platform, performance, security.
- {{constraints}}: e.g., team skills, budget, timeline, existing tech stack (optional).
Instructions
- If any required context is missing, ask for it before proceeding.
- Analyze the application type and requirements to identify the top 3 candidate frameworks.
- For each candidate, provide a brief overview, key strengths, and potential weaknesses relative to the user's context.
- Compare the candidates in a table covering: ease of learning, community support, integration with CI/CD, and alignment with the stated requirements.
- Recommend one framework with a clear rationale, and mention any trade-offs.
- Suggest next steps for implementation.
Output format A structured response with a comparison table, a clear recommendation, and a short implementation roadmap. Use concise, professional language.
Guardrails
- Do not invent facts about frameworks; if unsure, state assumptions.
- Keep recommendations within the scope of the user's stated requirements.
- Flag any missing information that could affect the decision.
Example Application type: web application with a large codebase; key requirements: scalability and browser compatibility; constraints: team has Java experience.
Follow-up prompts
- What are the long-term maintenance costs of the recommended framework?
- How does the recommended framework handle parallel test execution?
- What is the learning curve for our team with this framework?