Comprehensive Web App Manual Testing -- 2
Budget: $10 – $100 USD
I have a production-ready web application that now needs a fresh set of eyes. The task is purely manual QA with three clear focal points: functionality, usability, and security.
Here’s how I picture the engagement: you will explore every user-facing path, deliberately stress edge-cases, and note anything that breaks flow or compromises data. All findings should be captured in a concise bug log that includes steps to reproduce, expected versus actual behavior, severity, screenshots (or short clips), and your recommendation for fix priority.
Deliverables
• Full test plan or checklist showing coverage across functionality, usability, and security
• Detailed issue report (spreadsheet or tracker export)
• Final summary that highlights critical risks, quick wins, and overall product health
Acceptance criteria
1. Every core workflow is covered and documented.
2. All high-severity issues include reproducible steps and evidence.
3. Final report is clear enough for developers to act on without follow-up questions.
Current tech stack is a standard modern front-end (React) served by a REST API, so familiarity with browser dev tools, network inspectors, and common security test techniques (e.g., input fuzzing, basic auth checks) will be valuable. Cross-browser testing should at minimum include Chrome, Firefox, Safari, and Edge on desktop.
Once I confirm the reports meet the criteria above, the milestone is complete and we can discuss any follow-up regression passes.
Here’s how I picture the engagement: you will explore every user-facing path, deliberately stress edge-cases, and note anything that breaks flow or compromises data. All findings should be captured in a concise bug log that includes steps to reproduce, expected versus actual behavior, severity, screenshots (or short clips), and your recommendation for fix priority.
Deliverables
• Full test plan or checklist showing coverage across functionality, usability, and security
• Detailed issue report (spreadsheet or tracker export)
• Final summary that highlights critical risks, quick wins, and overall product health
Acceptance criteria
1. Every core workflow is covered and documented.
2. All high-severity issues include reproducible steps and evidence.
3. Final report is clear enough for developers to act on without follow-up questions.
Current tech stack is a standard modern front-end (React) served by a REST API, so familiarity with browser dev tools, network inspectors, and common security test techniques (e.g., input fuzzing, basic auth checks) will be valuable. Cross-browser testing should at minimum include Chrome, Firefox, Safari, and Edge on desktop.
Once I confirm the reports meet the criteria above, the milestone is complete and we can discuss any follow-up regression passes.