Critical flow scenarios
Written step lists for every flow that moves money or data, repeated identically each release.
Functional testing
We verify the product actually does what it promises by running the critical flows end to end.
We run every flow that moves money or data — sign-up, login, search, basket, checkout, cancellation — from end to end. We work with written scenarios and exploratory sessions in parallel: scenarios catch the known risks, exploratory testing catches what nobody thought of.
From the checklist
62 check items
Exploratory sessions
Time-boxed sessions with no script. This is where the paths nobody thought of turn up.
Boundary and error cases
Empty, overlong, negative, double-clicked, disconnected — everything off the happy path.
Data integrity checks
Whether records stay consistent when a transaction is interrupted halfway.
How we run it
- We list the critical flows with you and write a step-by-step scenario for each one.
- Testers in the network work through the scenarios on their own devices, recording every step.
- Time-boxed exploratory sessions run in parallel — this is where off-script paths get tried.
- Every finding is independently reproduced by the core team before it enters the report.
What you get
- A finding list ranked by severity, each with reproduction steps
- Screen recording, console and network log per finding
- The scenario list with pass/fail status
Out of scope
- Code review and writing unit tests are out of scope.
- Behaviour under load belongs to performance testing; this covers single-user scenarios.
What this typically turns up
- Double-tapping pay creates two separate orders
- A coupon combined with instalments computes the wrong total
- An interrupted sign-up leaves an unverified account behind
Questions about this service
Do you write the scenarios?
Yes. You give us the list of critical flows and any existing test documents; we write the scenarios and put them to you for approval.
Who provides the test data?
Test accounts and payment sandbox keys come from you. We generate the rest; we never work with live customer data.
What happens to a finding that cannot be reproduced?
It doesn't enter the report. Nothing goes on the list that the core team could not reproduce independently.
Included in
ScoutOne product, one test, 3 business daysReleaseWhole product, 3 platforms, pre-launchFleetRegression every release, monthlyEnterpriseRegulated sectors, custom SLA
Other services
Regression testingDid the new release break the old oneCompatibility matrixReal device and browser matrixPerformance & loadLoad speed and behaviour under loadSecurity reviewApplication review on the OWASP Top 10API testingSchema, error codes and boundariesPayment testingPayments, refunds and subscriptions with real cardsAccessibilityWCAG 2.2 AA and screen readersUsability reviewFlows that work but wear people downLocalization testingCountry by country, with native speakers
Don't test the next release alongside your users.
Sign up in the panel, pick what you want tested, pay. The first findings start landing in the same panel within hours.