Software testing
We test software we build and software built by others. Our testers work independently of the developers, and report what they find.
| Type of testing | What it answers | How |
|---|---|---|
| Functional | Does each feature do what the requirement says? | Test cases traced to requirements |
| Regression | Did the latest change break something that worked? | Automated suites run on every release |
| Integration | Do the system and its connected services agree? | End-to-end scenarios across APIs |
| Performance | Will it cope with real numbers of users? | Load and stress tests with reported limits |
| Security | Can it be misused or broken into? | Vulnerability scanning and common attack checks |
| User acceptance | Will the people using it accept it? | Guided sessions with your users and sign-off |
| Usability & accessibility | Can everyone use it on the devices they have? | Device, browser and accessibility checks |
Software quality assurance
Quality assurance looks at the process that produces software. We set standards, check they are followed and measure the results.
- QA plans and quality standards for each project
- Requirement, design and code reviews
- Defect tracking with root-cause analysis
- Release readiness criteria and go/no-go reviews
- Quality metrics reported to project sponsors
What every test cycle produces
Test plan
Scope, approach, environments and entry and exit criteria, agreed before testing begins.
Defect log
Every issue with steps to reproduce, severity and status, visible to you throughout.
Test summary report
What was tested, what passed, what remains open, and a clear recommendation on release.
Releasing soon?
We can test an existing system independently before it goes live.