Web App Smoke Test Plan
By Mo · Published · Updated
Produces a short browser test plan for a web app that covers the critical paths and different data states, with a screenshot as evidence for each check.
Prompt template
## Web App Smoke Test Plan Write a smoke test plan I can run in a browser after each release. - App and URL: [text: Name and address of the environment to test] - Critical user paths: [textarea: The three to six things users must always be able to do] - Roles: [multi: Visitor, Signed-in user, Admin, Paying customer] - Data states to cover: [multi: Empty, Few items, Many items, Error from server, Slow network] - Devices: [multi: Desktop, Tablet, Phone] - Time budget: [number: 5, 60] Pick the paths where a failure would cost users or revenue, and cut anything that does not fit the time budget in minutes. For each path write numbered steps, the exact result expected at the end, and one named screenshot to capture as evidence. Add one check for each selected data state on the pages where it matters most, such as an empty list that shows a helpful message and a failed request that shows an error instead of a blank page. Check each role sees only what it should. Add a phone-width pass for layout breakage on the main path. Include a console check: no red errors on load. Return a table with the path, steps, expected result, and screenshot name, then a pass or fail log template and the rule for when a failure should block the release.