Evidence
Client stories
Evidence from test strategy and QA automation consultations—specific enough to be useful, careful enough to stay confidential.
Voices from recent work
“StoneCore spent two days with our Melbourne squad walking through the payment release checklist. The automation backlog they left us was blunt about flaky suites we had been ignoring.”
— Priya N., Engineering Manager — fintech product team
“We asked for a lighter touch than a full rewrite. They still flagged that our API contract tests were covering the wrong boundary. Slightly uncomfortable, but accurate.”
— Marcus L., Head of QA — retail platform
“The readiness assessment before our catalogue migration named three environments we had never treated as production-like. We delayed a week. That call was unpopular in the moment and correct afterwards.”
— Elena K., Delivery Lead — marketplace business
“Retainer calls stay short. When we floated hiring two automation engineers instead of fixing ownership of the existing suite, they pushed back with a one-page hiring brief rewrite. Helpful, if a bit direct.”
— Tom H., VP Engineering — B2B SaaS (Australia)
Extended story: payments release checklist
A Melbourne fintech team approached StoneCore three weeks before a regulatory-facing payments release. Their UI automation suite was large, mostly green, and rarely caught the defects that had escaped in the previous quarter. The Test Strategy Engagement focused on release criteria already written in their programme plan—then mapped each criterion to evidence sources that actually existed.
Findings concentrated on three themes: over-reliance on end-to-end paths for pricing rules better covered at API level; missing soak checks in a staging environment that lacked realistic settlement data; and unclear ownership when a flaky suite blocked the release train. The written strategy reordered the automation backlog and named which checks could be retired without increasing risk. The team kept their framework; they changed what it was asked to prove.
Extended story: catalogue migration hold
A retail platform scheduled a catalogue migration across two brands. StoneCore ran a Release Readiness Assessment against the stated go-live criteria. Evidence for rollback drills was thin, and one “production-like” environment still pointed at a shared inventory service used by live traffic. The recommendation was a short hold with a concrete punch list rather than a vague “more testing.” Leadership accepted the hold; migration completed the following week with the shared dependency isolated.