Test charter and scenario planning
Understand the current setup and agree the decisions this part of the work depends on.
Manual Functional & Exploratory Testing
Investigate how an application behaves across normal, unusual and interrupted user journeys.
Manual Functional & Exploratory Testing
UnderstandImplementVerify & handover
Illustrative workflow. No customer records, traffic figures or test results are shown.
THE WORK
What this engagement can include
This service focuses on manual functional & exploratory testing. We agree the exact platforms, deliverables and acceptance criteria before implementation, so the proposal describes a bounded piece of work.
Functional and exploratory sessions
Implement the agreed behavior in a suitable environment and share it for review.
Defect evidence and retest results
Exercise the important paths and document the result, limits and next operating steps.
A POSSIBLE ENGAGEMENT
How this could work in practice
A new onboarding flow is checked with missing fields, expired sessions and users who navigate backward or retry an action.
This is an illustrative scenario, not a claim about a completed client project.
EVIDENCE & HANDOVER
How we check the work
Evidence of explored scenarios, reproducible defects and retest results for the fixes included in the engagement.
What you receive at handover
The agreed implementation or assessment, the relevant verification evidence, known limitations and instructions for the tasks your team will own. Access and source ownership, third-party licenses and any ongoing support are identified in the proposal.
See our project process →What we need from you
Requirements or expected behavior, supported environments, test data and access to the relevant user roles.
A named decision maker helps resolve questions, approve the scope and review work at the agreed checkpoints.
What we agree separately
Manual testing complements automation rather than exhaustively covering every possible state. The test window and boundaries are defined.
Requirements discovered during the work are reviewed before they are treated as additional deliverables. Timelines and fees follow the approved scope.
YOUR QUESTIONS
Before we get started
What if the requirements are incomplete?
We document assumptions and raise behavior questions during testing. An accountable product owner decides whether an observed behavior is acceptable.
What should we share in the first conversation?
Requirements or expected behavior, supported environments, test data and access to the relevant user roles. If those details are incomplete, start with the problem, the current setup and the outcome you need. We can identify what must be clarified before quoting the work.
How will scope, timing and acceptance be agreed?
We review the requirements and dependencies, propose deliverables and milestones, and define who approves the result. For this engagement, verification includes: Evidence of explored scenarios, reproducible defects and retest results for the fixes included in the engagement.
CONNECTED SERVICES
Explore related work
Need a different part of qa & test automation? These are separate scopes that can be combined when the project requires them.
QA & Test Automation
Start with what needs to work better.
Tell us about your current setup, the problem and any deadlines. We’ll discuss whether this service is the right fit before proposing the work.
Discuss your project