01
The Challenge
Releases relied on manual QA checking a spreadsheet of test cases before every deploy, which was slow, inconsistent, and increasingly couldn't keep up with release frequency, letting regressions slip through.
02
The Approach
1
Built a pytest-based test suite covering critical business logic, prioritized by which areas had historically produced the most production bugs.
2
Added Selenium-based end-to-end tests for core user flows (signup, checkout, core dashboard actions).
3
Integrated the test suite into CI so pull requests can't merge without passing tests.
4
Set up code coverage tracking to make testing gaps visible over time rather than assumed.
03
The Outcome
Regression bugs reaching production dropped noticeably after the pipeline went live, and release confidence improved enough that the team increased deployment frequency.