E2E Testing Patterns
Keeps browser test suites from decaying into flaky maintenance work.
Install
/plugin marketplace add wshobson/agents; /plugin install developer-essentials
When end-to-end tests are being written, a suite turns flaky, or browser tests go into CI.
- Author
- wshobson
- License
- MIT
Covers Playwright and Cypress with the rules that decide whether a suite survives its first six months: stable selectors from roles and test ids instead of CSS chains, waiting on conditions rather than fixed timeouts, and page objects so a UI change touches one file. It also draws the line on what belongs at this level — critical journeys like login and checkout, not edge cases better served by unit tests. Debugging gets its own section: headed runs, trace viewer, and test steps that make a CI failure readable.
Similar skills
Webapp Testing
SkillPlaywright-driven checks against a web app running on localhost.
Debugging and Error Recovery
SkillStops the line on an unexpected error and works down to the root cause.
Debugging Strategies
SkillReplaces guess-and-check debugging with a narrowing procedure.
Comments(0)
Sign in to comment