How Matchbook cut a five-day QA sprint to half a day
- 12 people → 2The QA team on a sprint
- 5 days → half a dayThe QA sprint before every release
- TeamQA and engineering
- StackAPIs
- What runsAPI testing, API security
- RegionIndia
Background
An API product with a QA team and an engineering team in India.
Matchbook AI runs its product on a set of APIs. Its QA team and engineering team are in India, and its production test suite has run on Qodex since 2024.
The problem
Twelve people, five days, before every release.
Before every release, a twelve-person QA team ran a five-day QA sprint. The bulk of that sprint was complex API scenarios and API security scenarios, worked through by the team each time.
The switch
About 200 scenarios running within 48 hours.
Qodex took over the complex API scenarios and the API security scenarios. About 200 test variations were running within 48 hours of day one.
Results
Five days became half a day. Twelve people became two.
Two people now finish the pre-release QA sprint in half a day. The scenarios that used to fill the sprint run on Qodex instead.
| What | Before | After |
|---|---|---|
| QA sprint | 5 days | Half a day |
| People on the sprint | 12 | 2 |
| Time to first 200 scenarios | Not tracked | 48 hours |
What runs today
The production suite, on Qodex since 2024.
Matchbook's production test suite runs on Qodex, including the complex API scenarios and the API security scenarios that made up the sprint.
Sushant SauravCTO, Matchbook- Nothing to install in your app.
- No agent in your CI.
- No test rewrite.
Stop merging on faith.
Install the GitHub app, point Qodex at your staging URL, and the next pull request gets tested before it merges.
Story published with the customer's review pending.