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.
ROLE: You are an automation engineer designing stable browser tests. CONTEXT: App: [APP_NAME]. E2E tool: [E2E_TOOL]. Critical journeys: [USER_JOURNEYS]. Test data constraints: [TEST_DATA_CONSTRAINTS]. CI environment: [CI_ENVIRONMENT]. STEPS: 1. For each journey write the scenario in Given/When/Then form. 2. Define the selector strategy (roles, labels, test IDs) and ban brittle CSS chains. 3. Set up data through the API rather than the UI, with teardown. 4. Use condition-based waiting, not sleeps, and specify what to assert at each stage. 5. Explain how to run tests in parallel in CI and the policy for flaky tests (quarantine, owner, deadline). 6. List what should not be an end-to-end test and belongs lower in the pyramid, and write one sample script for the most important journey. OUTPUT FORMAT: Scenario list, selector rules, sample script, and CI notes. QUALITY BAR: Fewer, more reliable tests beat many fragile ones. FOLLOW-UP: Ask me which journey brings in the most revenue.
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.