Free tool
How mature is your QA process, really?
Nine questions about how your team actually works, not how it is supposed to. You get a maturity level, a score for each of nine dimensions, and the specific gaps worth fixing first. Two minutes, no signup, and the scoring is published.
Nine questions, about two minutes. Nothing is sent anywhere unless you ask for it.
The five levels of QA maturity
Maturity here is not about how many tests you have. It is about how predictable your quality is: whether a good release depends on the right person being available, or on a process that works regardless of who is on shift.
Ad hoc
Quality depends on individuals remembering to check things. It works until someone is on leave, the deadline moves, or the person who knew the system leaves.
Repeatable
Testing happens consistently and is written down, but it is mostly manual and mostly at the end. Quality is a stage the work passes through rather than a property of how it is built.
Defined
You have real automation, a pipeline, and agreed ways of working. The gaps now tend to be in the areas nobody owns: environments, non-functional testing, or what actually blocks a release.
Managed
Quality is measured and enforced rather than assumed. You catch most defects before users do, and you can say why you believe a release is ready.
Optimising
Quality is designed in, measured over time, and used to make release decisions. Defects are treated as signals about the process, not just as tickets.
What the assessment looks at
One question per dimension. Each is somewhere teams commonly stall, and each is something you can change without rebuilding how you work.
Regression testing
How is regression testing run before a release?
Automated coverage
How much of your critical user journeys are covered by automated tests?
Pipeline gating
What happens when tests fail in your pipeline?
Environments and test data
How do you get a realistic environment and test data?
Defect management
What happens when someone finds a bug?
Performance and security
When do you test performance and security?
Release readiness
How do you decide a release is ready to ship?
When QA gets involved
At what point does QA first get involved in a feature?
Quality metrics
What do you track about quality?
Already know your gaps? Put a number on them.
If this assessment tells you defects are getting past you, the bug cost calculator works out what those escapes cost per year, where the money goes, and how much earlier detection would recover.
Open the bug cost calculatorQuestions about the assessment
How is the QA maturity score calculated?
Each of the 9 questions scores 0 to 3, in the order the answers are listed, for a maximum of 27. Your total falls into one of five bands, and every band and its threshold is published on the results page.
What are the five QA maturity levels?
Level 1, Ad hoc: Quality depends on individuals remembering to check things. It works until someone is on leave, the deadline moves, or the person who knew the system leaves. Level 2, Repeatable: Testing happens consistently and is written down, but it is mostly manual and mostly at the end. Quality is a stage the work passes through rather than a property of how it is built. Level 3, Defined: You have real automation, a pipeline, and agreed ways of working. The gaps now tend to be in the areas nobody owns: environments, non-functional testing, or what actually blocks a release. Level 4, Managed: Quality is measured and enforced rather than assumed. You catch most defects before users do, and you can say why you believe a release is ready. Level 5, Optimising: Quality is designed in, measured over time, and used to make release decisions. Defects are treated as signals about the process, not just as tickets.
Does this compare my team against other companies?
No, and that is deliberate. Saying you scored better than some percentage of teams would need a dataset of real companies, and we do not have one. You get a level and a list of specific gaps instead, which is something we can stand behind.
Do I need to give my email to see the result?
No. The result appears as soon as you answer the last question and nothing is gated. If you want it as an email you can forward to your team, that is optional.