QA audit
Find out where the risk is and what to test first.
- Coverage review
- Risk map
- Prioritised test plan
- Tooling recommendation
04 services / software qa & testing
I set up quality assurance that fits the team: a clear test strategy, automated suites for the web and the API, performance checks and a release process that catches regressions before they reach production. Manual testing where it matters, automation everywhere it repeats.
// what you get
// typical engagements
Starting points, not rigid packages. Every project gets a written scope and a fixed or weekly price before work begins.
Find out where the risk is and what to test first.
A maintainable automated suite for the flows that matter, running in CI.
A tester on every release, with the regression suite kept current.
// process
Walk the product with the team, learn the user journeys and where failures hurt most.
A risk-based test plan: what is automated, what is tested by hand, and what is deliberately skipped.
Critical paths first. Stable, readable tests that fail for real reasons, not flakiness.
Suites run on every pull request and nightly, with results the whole team can read.
A release checklist, an exploratory pass, and a short report on what was covered.
// related work
A QA audit, a Playwright and API automation suite running on every pull request, and a release process that cut escaped bugs by two thirds for a B2B SaaS team with no dedicated tester.
// tools
// faq
Both. Automation for anything that repeats (regression, APIs, smoke tests) and manual, exploratory testing for new features and releases, where a human finds what scripts cannot.
Playwright or Cypress for the browser, Postman and code-level tests for APIs, k6 or JMeter for load. If your team already has a framework, I work in it.
Yes. Most QA work is on existing products. The audit week is designed exactly for that.
Flaky tests are a design problem, not a fact of life. Suites are built with stable selectors, proper waits and isolated test data, and I measure flake rate as part of the monthly report.
Separately or together. Some clients want an independent tester on a build I am doing; others only need QA on a product their own team builds.
Tell me what you are building, what is slow, or what you are raising. I reply to every message personally.