Test Maintenance

​

Keep Tests Healthy with Minimal Effort

​

Essentials

• Prefer regeneration over manual rewrites for broad changes
• Apply auto-healing for selector drift, waits, and fixtures
• Use diff scope to update only impacted tests
• Keep PRD and acceptance criteria current

​

Shift Left (TDD with TestSprite)

• Use testScope: "diff" to target in-progress changes
• Run small subsets frequently via testIds
• Let healing suggestions guide selectors, waits, and data setup from the start

​

Common Tasks

• Update changed flows
  • Create Tests for New Change
• Fix failing or flaky tests
  • Healing & Observability
  • Rerun quickly: testsprite_rerun_tests({ projectPath: "/abs/path" })
• Expand coverage
  • Add Extra Tests
  • Test Types & Lifecycle
• Migrate existing suites
  • Import Existing Tests

​

Tips

• Use semantic selectors and explicit ready states
• Keep deterministic test data and clean state between cases
• Commit changes frequently so diff-based updates are accurate
• Run a small subset (by testIds) while iterating

​

Where Artifacts Live

• Results, PRD, plans, and logs under testsprite_tests/
• Reports: Markdown/HTML plus machine-readable JSON for automation

​

Related

• Create Tests for New Projects
• Modify or Update Tests
• MCP Testing Workflow
• MCP Tools Reference