End-to-End Test Scenarios From User Journeys
Define stable browser tests for critical paths.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Define stable browser tests for critical paths. Product and critical user journeys: [PRODUCT_AND_JOURNEYS]. Test tool and language: [TEST_TOOL]. Environments and test data options: [ENVIRONMENTS_AND_DATA]. Known flakiness: [FLAKINESS]. Return tables: 1. Journey selection: Journey | Business value | Frequency | Failure impact | Include in end-to-end suite? (only the few that must never break). 2. Scenarios: ID | Journey | Preconditions | Steps | Expected results | Data setup and cleanup | Risk. 3. Locator strategy: how to select elements (roles, labels, and stable test attributes rather than CSS paths or text that changes). 4. Stability rules: waiting for conditions instead of fixed pauses, isolating data per test, resetting state, avoiding dependency on third-party sites, controlling time and randomness. 5. Suite design: what runs on every pull request, what runs nightly, parallelization, retries (limited, tracked), screenshots and traces on failure. 6. Reporting and ownership: who fixes failures, quarantine policy for flaky tests, and a flake rate target. Provide example test code for two scenarios in my tool, with comments, and explain what should be tested at lower levels instead. Keep the suite small.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.