Doing it well with little.
WHAT SMALL TEAMS FACE
No dedicated testers No test environments No time allocated Pressure to release
WHAT TO DO FIRST
Identify what must never break.
WHAT TO AUTOMATE
Those paths, and nothing else initially.
WHY
A small reliable suite is worth more than an aspirational large one.
WHAT TO ADD NEXT
Tests for every defect found in production.
WHY THAT ORDER
It grows the suite exactly where defects actually occur.
WHAT TO DO WITHOUT TEST ENVIRONMENTS
Containers, creating them per run.
WHAT TO DO ABOUT MANUAL TESTING
A written checklist of what to verify before release.
WHY WRITTEN
Memory omits items under pressure.
WHAT TO PUT ON IT
The critical paths Anything that has broken before Anything affected by this change
WHAT TO ADOPT CHEAPLY
Static analysis Dependency scanning Automatic checks in the pipeline
WHY THOSE FIRST
They cost almost nothing to run and find real problems.
WHAT TO PRIORITISE ABOVE MORE TESTING
The ability to detect problems in production and reverse quickly.
WHY
It bounds the damage of everything you did not test.
