The problem
Supply-chain planning software is dense: big data sets, screens that depend on each other, and long workflows that planners run every day. End-to-end tests written one at a time against that kind of UI get slow to write and expensive to keep green. The team needed a shared foundation, not more one-off scripts.
What I built
- A UI and interface automation framework, designed from scratch in TestCafe and TypeScript, with shared fixtures, reusable libraries and patterns that let the suite grow without each test reinventing setup.
- Functional, regression and end-to-end tests on top of it, kept maintainable as the product changed.
- Automated regression wired into CI/CD pipelines, so every change got release feedback without anyone asking for it.
QA prime on epics
For the epics I owned, I was the quality lead from start to finish: shaping acceptance criteria with the team, defining the test strategy, running exploratory testing where automation wasn’t the right tool, and giving a clear read on release readiness and its risks.
Raising the bar around me
- Investigated failures, then documented and triaged Jira defects with developers through to resolution.
- Presented better testing approaches to cross-functional teams.
- Introduced reusable framework libraries and test fixtures, and mentored junior testers on automation and quality practices.
Tools
TestCafe, TypeScript, JavaScript, Node.js, CI/CD pipelines, Jira.