Functional QA, the bread and butter of testing.
Full coverage against the specs and design documents. Every bug filed with repro, platform, severity and attachments. A weekly report you can act on without a meeting.
Request a quote →End-to-end manual testing led by the same senior all engagement.
End-to-end manual functional testing against your design spec and platform requirements. We start exploratory - building a picture of how the game actually plays before we start focusing on test cases - then move into structured regression as the build stabilises.
Every session is logged and every bug is filed with a reproduction path a developer can follow in under five minutes. Severity is assigned using a consistent framework so your team always knows what to fix first.
What you get at every stage
- Clear, to the point bug reports. All attachment and necessary details filled in.
- Weekly written report with coverage map, findings, risks, what's next
- Retests confirmation on each fix before the report goes out
- Handover artifacts at close: test plans, cases, coverage, open issues
- Named senior contact throughout - no rotation
How a functional QA engagement runs
Brief & scope
You send the brief. We ask exactly what we need - platforms, genres, deadlines, known risks. Back to you with a scope and timeline in 48 hours.
Test strategy
We write the test plan before we touch the build. Coverage areas, risk zones, reporting schedule - agreed and documented before day one.
Exploratory pass
First week is exploratory - learning the game as it actually is, not as the specs want it should be. This way we make sure to find the unexpected things checklists miss.
Structured regression
As the build stabilises we shift to structured test runs and regression. Every fix is retested. Coverage tracked against the plan. Weekly report every Friday.
Handover
Engagement closes with a full handover document: test plan, case library, coverage map, open issue list by severity. Nothing lives only in our heads.