Manual and functional QA

Not everything should be automated. We combine structured test design with exploratory testing to find the defects scripts miss, and to protect the journeys your users care about most.

Talk to us about thisSee how we work

What you get

  • A risk-based test plan and test cases
  • Exploratory testing sessions with clear notes
  • Regression and smoke test suites
  • Acceptance (UAT) support
  • Defect reports with steps, evidence and severity
  • A weekly quality summary in plain language

How we do it

  1. UnderstandWe learn your product, users and the risks that matter most.
  2. DesignWe design tests around real user journeys and business rules.
  3. TestWe run tests, log defects and triage them with your team.
  4. ReportWe report clearly and retest every fix before release.

What a bug report from us looks like

Every defect we log is written so a developer can reproduce it on the first try. This is a sample.

CHK-214Severity: HighPriority: P1Status: Ready for fix

Discount code is applied twice when the user goes back from the payment page

Environment
Staging build 2.14.0 · Chrome 130 on Windows 11 · test account qa.buyer3
Steps
  1. Add an item priced ₹1,250 to the cart.
  2. Apply the code SAVE10 on the cart page.
  3. Continue to payment, then press the browser Back button.
  4. Continue to payment again.
Expected
One 10% discount. Order total ₹1,125.
Actual
The discount is applied a second time. Order total ₹1,012.50.
How often
5 out of 5 attempts. Not reproducible on the live site, which is on build 2.13.
Evidence
Screen recording and network log attached. The /cart/apply-coupon call fires again on the second visit.
Impact
Revenue loss on every affected order once 2.14 ships. Blocks the release.

Tools and approach

We choose what fits your stack and team.

JiraTestRailPostmanBrowser developer tools

A good fit if…

  • You release often and full regression takes too long by hand
  • Your product has complex business rules
  • You want fresh eyes before a major launch
  • You want a plan to automate the right things first

Where this fits

This tends to matter most for teams in fintech, healthcare and insurance. It pairs well with test automation, and with QA and automation transformation. The services overview shows how everything we do fits together.

Common questions

Do you only do manual testing?

No. Manual testing is the foundation. We automate repeatable checks and keep manual effort for exploratory, usability and judgement-heavy work.

Can you work inside our sprints?

Yes. We join your planning, stand-ups and reviews, and test within the sprint wherever possible.

Talk to us about manual and functional QA

Tell us what you’re working on and we’ll suggest a clear first step.

Talk to us about this