Field notes from the world of QA automation — lessons learned, problems solved, and patterns worth sharing.
When I joined Automobilmart, the team had great API tests but zero contract coverage. Writing Pact interactions by hand was tedious, error-prone, and nobody was doing it. Here's how I built a library to fix that.
At Worknoobs, I inherited a suite with endemic flakiness. This is my systematic method for diagnosing and eliminating flaky tests — covering async races, shared state, and external dependencies.
What does a genuine QA engagement report look like? Here's a breakdown of my methodology for the Worknoobs escrow platform — from suite architecture review to prioritised risk register.
They were already paying for infrastructure they didn’t need because "the system couldn’t handle load." The real problem wasn’t the system — it was the tests. Fixing that changed everything.
I didn’t want another ORM that just “looks like Mongoose.” I wanted one that enforces correctness — at runtime and at compile time. Today was about closing that gap.