ADN · QA
Confirmed QA · 2024
Visit the site
Quality that holds up to 200,000 monthly subscribers.
The need
On a high-traffic platform, every regression is expensive: a payment bug or a degraded simulcast is immediately visible to hundreds of thousands of users. API tests lived in opaque collections maintained by a single person.
My contribution
Front and back test campaigns, API collections and acceptance testing before every simulcast.
What was delivered
Calm production releases on a critical platform, API tests reviewed like code, and a ramp-up that led to backend development.
What I built
A systematic testing approach, from front to back, that goes with every release.
Test campaigns
Acceptance testing before every simulcast.
Front and back campaigns, regression testing before every release, bug triage and fix follow-up.
Jest · TypeScript
API collections
API tests reviewed like code.
Collections first in Insomnia, then migrated to Bruno: plain-text files versioned with the code, reviewed in PRs, run in CI.
Insomnia · Bruno
Payment
Stripe payments, tested.
Stripe payment tests, on a platform where a payment bug is immediately visible.
Stripe
Continuous integration
A quality process in CI.
The quality process is wired into CI, so tests run without anyone having to think about it.
CI/CD
Tech stack
- API tests
- InsomniaBruno
- Automation
- JestTypeScript
- Payment
- Stripe
- Continuous integration
- CI/CD

