Manual QA · Web and software

QA that follows the paths real users take.

Independent manual testing for websites and web products, with clear evidence, useful defect reports and attention to the context behind each release.

Find the risk before your customers do.

A checklist alone does not show how a product behaves. I learn the intended flow, question assumptions, reproduce failures carefully and report what a developer needs to act. Work can cover a single launch, a regression cycle or an ongoing product team.

  • Exploratory testing

    Realistic behaviour and edge cases beyond the scripted happy path.

  • Regression testing

    Important existing journeys protected when a release brings new changes.

  • Responsive and browser QA

    Interfaces checked across the screen sizes, browsers and devices that matter.

  • Actionable reporting

    Reproduction steps, evidence, environment, impact and appropriate severity.

What is included

A complete, clearly scoped delivery. The quotation lists exactly what your project covers.

  • Test scope and risk review
  • Functional and exploratory testing
  • Responsive and browser coverage
  • Regression runs
  • Clear defect reports
  • Release summary

How it runs

  1. 1

    Understand

    Review goals, requirements, known risks and the release context.

  2. 2

    Prioritise

    Focus on critical journeys and the areas most affected by change.

  3. 3

    Test and investigate

    Explore, reproduce, and separate defects from unclear requirements.

  4. 4

    Report

    Deliver actionable issues and a short view of the remaining release risk.

Professional manual QA, backed by hands-on development and responsibility for live production products.

See selected work

Questions before we begin

Do you test only websites?

Websites and browser-based products are the main focus, including responsive behaviour, user journeys and cross-browser compatibility.

Can you test before a one-off launch?

Yes. A defined pre-launch review can focus on the highest-risk paths and end with a prioritised report.

Do you write test cases?

Yes, when reusable regression coverage is worth it. For early or fast-changing work, exploratory charters are often more effective.

Can you work with an existing team?

Yes. Reports can fit your workflow in Jira, TestRail or whatever issue tracker the team already uses.

Related services

  • Website design

    Responsive business websites built around enquiries, appointments, trust, sales or information.

  • eShop development

    WooCommerce or Shopify stores, designed from product discovery through payment and order confirmation.

  • Chrome extension development

    Focused browser tools on Manifest V3, built around one workflow or operational task.

Let’s scope it properly.

Share the goal, the current setup and your deadline. I reply with useful questions and a clear quotation.