Assure — Service
Manual QA
Independent manual QA support to help products reach production on time and with greater confidence.
Testing done by the team that wrote the code finds the failures they thought to look for. An independent tester reads the requirement instead of the implementation, which is a different exercise and finds different things. You do not have to give us the development work to get this — most of our QA engagements are on applications somebody else built, and that independence is the point rather than a limitation.
Available as
- Independent manual QA
- Dedicated QA team
- QA team extension
- Release validation
- Short-term QA support
- Ongoing managed QA
What is included
- Requirement and acceptance-criteria analysis
- Test strategy, planning and test-case design
- Functional, smoke, sanity and regression testing
- Integration, system and end-to-end testing
- Exploratory and usability testing
- Cross-browser and responsive testing
- Mobile-application testing
- API testing and database validation
- User-acceptance testing support
- Defect reporting, triage and retesting
- Release-readiness review
- Test summary reporting
What changes
The difference this makes.
- 01
A documented view of what was tested and what was not, instead of an informal assurance
- 02
Defects raised with reproduction steps, environment and evidence attached
- 03
A release-readiness position you can act on, separate from delivery pressure
- 04
Traceability from requirement to test case, so coverage gaps are visible
In detail
Everything this service covers.
The full breakdown. Not every item applies to every engagement — scope is agreed against your requirement.
QA engagement shapes
From a single release validation to an ongoing managed QA function.
- Complete project QA
- Manual QA engineer
- Automation QA engineer
- Dedicated QA team
- Team extension
- Release validation
- Regression testing
- Automation framework setup
- Short-term QA support
- Ongoing managed QA
Manual testing coverage
- Requirement analysis
- Acceptance-criteria review
- Test strategy
- Test planning
- Test scenarios
- Test cases
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- End-to-end testing
- Exploratory testing
- Usability testing
- Cross-browser testing
- Responsive testing
- Mobile-application testing
- API testing
- Database validation
- User-acceptance testing support
- Production smoke testing
- Defect reporting
- Defect prioritisation
- Defect retesting
- Defect lifecycle management
- Release-readiness review
- Test summary reports
Nonfunctional testing
Offered where the capability is verified for your stack and environment.
- Performance testing
- Load testing
- Stress testing
- Accessibility testing
- Compatibility testing
- Basic security validation
What you receive
- Test strategy
- Test plan
- Test cases
- Requirements traceability
- Defect reports
- Test-execution reports
- Release-readiness report
- Final test summary
Scope and limits
What we will not claim.
These are on the page deliberately. A service description that only makes promises is the one that produces an argument later.
No testing process can guarantee zero defects. What we commit to is coverage against an agreed test plan, and a clear statement of what was tested, what passed and what remains open at the point of release.
On-time delivery is committed against an agreed scope, test plan, dependency list and approval schedule — not against a date set before the scope is known.
We do not advertise penetration testing. Basic security validation is included where relevant; specialist penetration testing should be commissioned from a verified specialist.
Considering manual qa?
Tell us what you are trying to achieve and what you already have in place. We will tell you what we would take on.