Automated Test Strategy

A written test strategy for your codebase: what to test at unit, integration and end-to-end level, fast feedback loops, coverage that means something, and the reviews that keep the suite trusted.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Automated Test Strategy, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

199

Starter tasks

⚙️ Software Engineering

Automated Test Strategy

Deciding what to test at which level, from unit to integration to end-to-end, so the test suite gives confidence without slowing everyone down.

  1. Test suite inventory by level and runtime
  2. Testing strategy one-pager for the codebase
  3. Risk map of the code that must not break
  4. Agreed definitions of unit, integration and end-to-end
  5. Test runner and framework choice per language
  6. Test folder layout and naming conventions
  7. Fast local test loop under ten seconds
  8. Pre-merge test gate by level
  9. Baseline suite health numbers
  10. Regression test with every bug fix
  11. Monthly suite health review
  12. Slowest tests sweep
  13. Coverage review of changed code
  14. Test checklist for pull request reviewers
  15. Skipped and disabled test audit
  16. Test data and fixture upkeep
  17. Quarterly test strategy review with the team
  18. Escaped defect review by test level
  19. Untested module backlog
  20. Unit tests that check behaviour, not implementation
  21. Test doubles, from stubs and mocks to fakes
  22. Test-driven development on real tickets
  23. Property-based testing for core logic
  24. Integration tests against real databases in containers
  25. Consumer-driven contract tests between services
  26. Mutation testing to measure test quality
  27. Snapshot and approval tests used sparingly
  28. Testing asynchronous and time-dependent code
  29. Rebalancing an inverted test pyramid
  30. Replacing mock-heavy tests with fakes
  31. Choosing which user flows deserve end-to-end tests
  32. Test runtime budget per level
  33. Coverage threshold policy
  34. Test impact analysis to run only affected tests
  35. Test data builders instead of giant fixtures
  36. Characterisation tests before a risky change
  37. Test plan for a major feature launch
  38. Test strategy workshop with the team
  39. Moving the suite to a new test runner
  40. Audit-ready test evidence for a compliance review
  41. Lean test strategy for a solo developer or small startup
  42. Adding tests to a codebase with none
  43. Setting test expectations as a new team lead
  44. Test strategy for a data pipeline team
  45. Component tests for a frontend team
  46. Team testing skills matrix
  47. Fuzzing parsers and input handlers for correctness
  48. Stateful property testing for complex workflows
  49. Test architecture for a multi-team monorepo
  50. Measuring what the test suite is worth

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Test suite inventory by level and runtime

Before anyone argues about the test pyramid, it helps to know the shape you actually have. Counting tests by level, measuring how long each level takes and noting which folders have none turns a vague feeling that the suite is slow or thin into numbers a team can plan against.

First tasks

  • Run the full suite once with timing output switched on and save the report
  • Tag each test folder as unit, integration or end-to-end in a spreadsheet
  • List production modules that no test file imports
  • Commit the inventory as a short document in the docs folder

Testing strategy one-pager for the codebase

Most teams test by habit, so each engineer brings the approach of their last job and the suite ends up with three styles and no agreement. A single page that says what each level is for, what must be covered before merge and what is deliberately left untested gives reviewers something to point at and new joiners something to read on day one.

First tasks

  • Write three sentences on what unit, integration and end-to-end tests are each for here
  • Ask the agent to turn your notes and the suite inventory into a first one-page draft
  • Circulate the draft to three engineers and collect comments within a week
  • Merge the strategy and link it from the pull request template

Risk map of the code that must not break

Not every line deserves the same testing effort: a typo in an admin label costs nothing, a rounding error in billing costs money and trust. Mapping the flows where failure is expensive (payments, permissions, data loss, anything regulated) tells the team where thorough testing pays and where a lighter touch is fine.

First tasks

  • List the flows where a bug would lose money, data or customer trust
  • Ask support which customer-facing failures came up most in the past year
  • Score each flow for impact and how often its code changes
  • Pick the three high-impact flows with the weakest tests

Make it yours.

Install Automated Test Strategy, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.