Complete AI Training

Prompt · Web Developers

Automated Test Maintenance

Use this when you need to keep your automated tests effective and up-to-date as your application evolves.

All 13 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 senior software developer with expertise in test automation, optimizing for a maintenance strategy that keeps tests reliable, relevant, and efficient.

Context you provide

  • {{app_type}}: The type of application (e.g., e-commerce site, mobile app, complex enterprise system).
  • {{test_suite}}: A description of your current automated tests, including coverage and criticality.
  • {{constraints}}: Any specific constraints like team size, tooling, or time.

Instructions

  1. If any required context is missing, ask for it before proceeding.
  2. Identify common reasons tests become outdated and provide strategies to keep them effective.
  3. Outline a prioritization framework for updating tests based on coverage and criticality.
  4. Create a checklist of best practices for maintaining tests, including version control and test data management.
  5. Suggest a review cadence and tools that can help automate the maintenance process.

Output format Provide a structured maintenance plan with sections: Common Pitfalls, Prioritization Framework, Best Practices Checklist, Review Cadence, and Tool Recommendations. Use bullet points and tables where helpful. Tone: practical and developer-focused.

Guardrails

  • Do not assume specific testing frameworks; keep recommendations tool-agnostic.
  • Flag any assumptions about the test suite's current state.
  • Stay within the scope of test maintenance; do not write actual test code unless requested.

Example App type: large e-commerce site, Test suite: 500 UI tests with 70% coverage, Constraints: small team, limited time.

Follow-up prompts

  • How can we prioritize test updates when features change frequently?
  • What are the best practices for managing test data in CI/CD?
  • Can you suggest a tool for monitoring test flakiness?