Exploratory testing
Investigate realistic behaviours and edge cases beyond scripted happy paths.
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.
01 / Approach
Find risk before your customers do.
A checklist alone does not reveal how a product behaves. I learn the intended flow, explore assumptions, reproduce failures carefully and report the information a developer needs to act. Work can support a single launch, a regression cycle or an ongoing product team.
Regression testing
Protect important existing journeys when releases introduce new changes.
Responsive and browser QA
Check interfaces across relevant screen sizes, browsers and devices.
Actionable reporting
Provide reproduction steps, evidence, environment, impact and appropriate severity.
02 / Included
A complete, clearly scoped delivery.
- Test scope and risk review
- Functional and exploratory testing
- Responsive/browser coverage
- Regression execution
- Clear defect reports
- Release summary
03 / Process
From useful questions to a dependable release.
- 01
Understand
Review goals, requirements, known risks and the release context.
- 02
Prioritise
Focus coverage on critical journeys and areas most affected by change.
- 03
Test and investigate
Explore, reproduce and distinguish defects from unclear requirements.
- 04
Report
Deliver actionable issues and a concise view of remaining release risk.
04 / FAQ
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 provide a prioritised report.
Do you write test cases?
Yes, when reusable regression coverage is valuable. Exploratory charters may be more effective for early or rapidly changing work.
Can you work with an existing development team?
Yes. Reports can fit the team's workflow in Jira, TestRail or its existing issue-tracking process.
06 / Start a project
Let’s scope it properly.
Share the goal, current setup and deadline. You will receive a practical response and a clear quotation.