How Mavim ships SSO-gated API changes in two days
- Two weeks → two daysShipping a complex API change
- Microsoft SSOThe auth flow Qodex drives end to end
- TeamPlatform engineering
- StackAPIs behind Microsoft SSO
- What runsEnd-to-end API scenarios, API security
- RegionNetherlands
Background
A Dutch software company whose APIs live behind Microsoft SSO.
Mavim is based in the Netherlands. Its APIs sit behind Microsoft SSO and browser-based authentication, and many of those APIs depend on that login flow before they will answer at all.
The problem
Every end-to-end test had to get through the login first.
Because so many of Mavim's APIs depend on the Microsoft SSO flow, end-to-end testing had to drive that browser-based login before it could touch the API. A complex API change took a couple of weeks to ship.
The switch
Qodex drives the SSO flow, then the scenarios.
Qodex runs Mavim's complex end-to-end API scenarios through the Microsoft SSO and browser-based authentication flow, so the scenarios reach the APIs the way a signed-in user does.
Results
Two weeks became two days.
A change that took a couple of weeks to ship now ships in two days.
| What | Before | After |
|---|---|---|
| Shipping a complex API change | Two weeks | Two days |
What runs today
End-to-end scenarios and API security, behind SSO.
Qodex runs Mavim's end-to-end API scenarios and API security scenarios through the Microsoft SSO flow.
Wouter Jan de BaanCPO, Mavim- 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.