01
Test strategy
What to test, how deeply and before which release.
Quality Assurance (QA) testers make sure your product does what it should before customers find out it does not. They plan what to test, find defects, check every release and automate the checks that matter most.
The mechanics built the car. The inspector checks the brakes, lights and steering before it goes on the road, so the first problem is found in the garage, not on the motorway.
Before they turn into complaints and lost customers.
So new features do not break old ones.
Repeat checks run by machine on every change.
If two or more of these sound familiar, add this role to your Product team.
What to test, how deeply and before which release.
Checking new features and re-checking existing ones.
Clear, reproducible bug reports the team can act on.
Automated checks that run every time code changes.
Volunteers give up to three hours a day, Monday to Friday, over three months or more. Daily and weekly updates keep you informed, and rapid feedback from you in the first two weeks makes the biggest difference.
Learns the product, tests the main customer journeys and reports the first defects clearly.
A test plan, a regular release check and the first automated tests running.
Fewer defects reaching customers, a growing automated suite and a handover for the next tester.
You do not need to be an expert to recruit well. Use these questions at interview and listen for the signs below.
Build the product. Screens, features and the logic behind them.
Read the guide →Captures what users need. Interviews and research, not assumptions.
Read the guide →Keeps you online. Hosting, monitoring and alerts so problems are spotted fast.
Read the guide →Create your company account, list an Opportunity with the matching template and start meeting Volunteers this week.