---
name: web-app-smoke-test-plan
description: "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. Use when a web app needs a short browser smoke test covering its critical paths, data states, and roles, with screenshot evidence. Do not use for automated end-to-end test code or exhaustive regression testing. Related topics: coding, technical."
---

# Web App Smoke Test Plan

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.

## When to use

Use this skill when a web app needs a short browser smoke test covering its critical paths, data states, and roles, with screenshot evidence. Do not use it for automated end-to-end test code or exhaustive regression testing.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Choose the critical paths whose failure would cost users or revenue and trim the list to fit the time budget.
3. Write numbered steps for each path with the exact expected result and a named screenshot as evidence.
4. Add one check per selected data state and role on the pages where it matters most.
5. Add a phone-width pass on the main path and a console check for errors on load.
6. Create a pass or fail log template and state which failures should block the release.

## Inputs

- **App and URL** (free text, e.g. "Name and address of the environment to test")
- **Critical user paths** (longer free text)
- **Roles** (choose any: Visitor, Signed-in user, Admin, Paying customer)
- **Data states to cover** (choose any: Empty, Few items, Many items, Error from server, Slow network)
- **Devices** (choose any: Desktop, Tablet, Phone)
- **Time budget** (number from 5 to 60)

## Output

A table of paths with steps, expected results, and screenshot names, followed by a pass or fail log template and a release-blocking rule.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Web App Smoke Test Plan

Write a smoke test plan I can run in a browser after each release.

- App and URL: {{App and URL}}
- Critical user paths: {{Critical user paths}}
- Roles: {{Roles}}
- Data states to cover: {{Data states to cover}}
- Devices: {{Devices}}
- Time budget: {{Time budget}}

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.

## Pitfalls

- Testing only the happy path with a full account, and missing the empty state a new user sees first.
- Writing steps like check that it works with no expected result, so two testers can disagree.
- Planning more checks than the time budget allows, so the plan is skipped.