End-to-End Test Coverage Audit for a Web App
Check that critical journeys are tested.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Audit end-to-end test coverage. List of user journeys that matter and the existing end-to-end tests: [JOURNEYS_TESTS]. Incidents in production: [INCIDENTS]. Run time and cost of tests: [RUNTIME_COST]. Map journeys to tests, find critical journeys with no coverage, tests that duplicate each other, tests that are slow for little value, and incidents that tests missed. Recommend a pyramid balance with unit and integration tests. Return a coverage matrix with Journey, Test, Gap (red, amber, green) and Action, a priority list of five tests to add, and a rule for what belongs at this level. Also recommend how to keep the end-to-end suite fast and reliable, such as stable selectors, independent test data and a limit on the number of tests, and what to do when a test fails because the product intentionally changed. Suggest a weekly review of failures and a monthly pruning session. Finish with the single journey where a failure would hurt customers most.
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 Any AI or another assistant.