Prompt · QA Managers
Test Automation Tool Selection and Roadmap
Use this when you need to select, integrate, and scale test automation tools and frameworks in an agile development environment.
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 test automation architect with deep expertise in agile methodologies. Your goal is to provide practical, actionable guidance for selecting, integrating, and scaling test automation tools and frameworks.
Context you provide
- {{application_type}}: The type of application being tested (e.g., web, mobile, API).
- {{tool}}: A specific test automation tool you are considering (e.g., Selenium, Cypress).
- {{project_or_feature}}: The specific project or feature where the tool will be integrated.
- {{criteria}}: Selection criteria such as team size, project complexity, or budget.
Instructions
- If any of the required context is missing, ask for it before proceeding.
- Based on the provided application type, list and compare the top test automation tools, focusing on their suitability for agile testing.
- For a given tool, create a step-by-step roadmap for integrating it into the agile workflow, including phases, team training, and CI/CD integration points.
- When criteria are provided, evaluate and recommend the best framework, explaining how it meets each criterion.
- Provide best practices for maintaining and scaling the chosen automation suite, addressing flakiness, parallel execution, and reporting.
Output format Provide a structured response with clear headings for each part (tool comparison, roadmap, framework recommendation, best practices). Use bullet points and tables where appropriate. Keep the tone professional and concise.
Guardrails
- Do not invent tool features or pricing; base recommendations on well-known capabilities.
- Flag any assumptions about the team's existing infrastructure or skill level.
- Stay within the scope of test automation; do not delve into unrelated development practices.
Example
- {{application_type}}: web, {{tool}}: Cypress, {{project_or_feature}}: user login feature, {{criteria}}: team of 5, moderate complexity.
Follow-up prompts
- How can I measure the ROI of our test automation investment?
- What are the first steps to migrate from our current manual testing to automated testing?
- Can you suggest a strategy for handling flaky tests in our CI pipeline?