Don't let your users QA your product.
Every release carries risk.
I find what breaks before it ships.
What happens without QA before release
Bug in production
Checkout fails on Safari 17 — total: NaNRelease readiness
- Login flow — verified
- Payment integration — 2 open issues
- Mobile breakpoints — not tested
- Accessibility audit — pending
What I test
- Happy path + negative cases
- Boundary values & edge cases
- Mobile + cross-browser
- Real user flows, not just specs
When to hire me
Case studies from real QA work
Concrete examples where testing reduced release risk, exposed performance limits or built a maintainable automation layer for business-critical flows.
E2E automation for a SaaS product with multi-market releases
Manual pre-release verification of the most critical flows took days and was inconsistent across market versions. Regressions in billing or login shipped undetected.
- Automation of critical scenarios before release
- Measured data for performance and stability decisions
- Maintainable coverage without unnecessary test duplication
Why address QA early
Cost reduction
A bug found before release costs far less than the same issue fixed in production.Release confidence
Before deployment, you know what was verified, where the risk remains and what still needs attention.Better decisions
QA is not just a list of bugs. It is input for prioritisation, release planning and future product work.How we work
Fast project understanding
We align on product type, scope, risk areas and the goal of the engagement.
Recommended approach
You get a clear recommendation on what to test now, what to automate and what output makes sense.
Testing execution
The actual testing runs, issues are reported continuously and automation can be prepared where relevant.
Output and next step
You leave with a prioritised issue overview, recommendations and a clear proposal for what should happen next.
QA insights & testing practice
The blog delivers practical QA experience: test strategy, Playwright, automation, accessibility and performance. Concise, concrete and immediately applicable in practice.
GEO and AEO: a new layer your website needs to pass
GEO and AEO are a new layer on top of classical SEO. They describe how well your website can be used by AI agents — and how to test it systematically.
How to design a Playwright regression suite that supports releases instead of blocking them
Regression automation should be fast, stable and tied to release decisions. If it is slow and fragile, the team will route around it.
Contact
Get in touch if you need a specific release tested, a QA process designed or meaningful automation built for your product.
Is your site ready for AI?
Check whether AI tools read your content correctly — or fill in the gaps themselves. A quick test that shows what AI sees and what it ignores.
Test my site