01 / FUNCTIONAL
Does it work?
Business workflows, validations, navigation, positive paths and alternate user journeys.
I’m Prathamesh Pawar, a Senior Test Engineer with 5 years of software testing experience. I combine structured test design with exploratory thinking to uncover the issues real users are likely to hit.
I bring a repeatable manual QA process to web products — from understanding the flow to documenting evidence a developer can act on.
Business workflows, validations, navigation, positive paths and alternate user journeys.
Negative inputs, edge conditions, unusual sequences and boundary-focused testing.
Unscripted exploration designed to expose behavior that planned cases don't anticipate.
Rechecking critical journeys after changes and looking for unintended side effects.
Precise reproduction steps, expected vs actual results, severity, priority and evidence.
Traceable QA documentation that makes the testing process transparent to clients and teams.
Every stage creates an output. Every failure has traceability. Every conclusion is backed by what was actually tested.
Input → Coverage → Evidence → Decision
Requirements, users, risks and business intent.
Scope, priorities, environments and coverage.
Scenarios, cases, data and expected behavior.
Execute, challenge flows and follow observations.
Defects, screenshots, severity and traceability.
Retest, assess risk and communicate quality.
I’d rather show one thoroughly tested product than a page of shallow demo projects. This case study is the first piece of a growing QA portfolio.
A structured end-to-end testing exercise covering test planning, scenario design, detailed test cases, negative and edge testing, exploratory testing, defect reporting, evidence collection and a final test summary.
PLATFORM: SAUCEDEMO · PROJECT NAME IS INTENTIONALLY KEPT GENERIC ABOVE
I’m a Senior Test Engineer with 5 years of software testing experience. My strength is combining disciplined test coverage with the curiosity to ask, “What happens if a real person does this differently?”
I’m building this portfolio deliberately: one substantial case study at a time, with more projects to follow. The goal is simple — give prospective clients a clear view of how I think, test, document and communicate.
Tell me what you're building, where you are in the release cycle, and what you want tested. I can help turn that into a focused manual QA engagement.