04 services / software qa & testing

Find the bugs before your customers do.

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.

A laptop screen showing lines of code under test

// what you get

Deliverables, not deliverable-shaped promises.

  • Test strategy and risk-based test plan for your product
  • End-to-end UI automation with Playwright or Cypress
  • API test suites with contract and negative-path coverage
  • Performance and load testing with k6 or JMeter, with a baseline report
  • Regression suites wired into CI so every pull request is checked
  • Exploratory and manual test passes before major releases
  • Bug reports developers can act on: steps, environment, evidence, severity

// typical engagements

Three ways to start.

Starting points, not rigid packages. Every project gets a written scope and a fixed or weekly price before work begins.

1 week

QA audit

Find out where the risk is and what to test first.

  • Coverage review
  • Risk map
  • Prioritised test plan
  • Tooling recommendation
Ask about this
from 3 weeks

Automation suite

A maintainable automated suite for the flows that matter, running in CI.

  • Framework setup
  • Critical-path E2E tests
  • API tests
  • CI integration & reporting
Ask about this
monthly

Release QA retainer

A tester on every release, with the regression suite kept current.

  • Release test passes
  • Suite maintenance
  • Bug triage
  • Monthly quality report
Ask about this

// process

How a testing engagement runs.

  1. 01

    Understand

    Walk the product with the team, learn the user journeys and where failures hurt most.

  2. 02

    Plan

    A risk-based test plan: what is automated, what is tested by hand, and what is deliberately skipped.

  3. 03

    Automate

    Critical paths first. Stable, readable tests that fail for real reasons, not flakiness.

  4. 04

    Integrate

    Suites run on every pull request and nightly, with results the whole team can read.

  5. 05

    Release & report

    A release checklist, an exploratory pass, and a short report on what was covered.

// related work

Case studies.

All work
QA & testing SaaS · 2025

Test automation and release QA for a SaaS platform

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.

-67% bugs escaping to production Case study

// tools

What I work with.

PlaywrightCypressSeleniumPostmanJestpytestk6JMeterGitHub ActionsAllureBrowserStackJira

// faq

Common questions.

Do you do manual testing or automation?

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.

Which tools do you use?

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.

Can you test an app you did not build?

Yes. Most QA work is on existing products. The audit week is designed exactly for that.

Will the tests be flaky?

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.

How does this fit with your development work?

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.

Have a project in mind?

Tell me what you are building, what is slow, or what you are raising. I reply to every message personally.