lsantosweb When to use
Use this skill for:
- Playwright or Cypress setup
- end-to-end testing of critical flows
- CI test pipeline setup
- regression suites
- visual regression
- reproducing bugs through automation
- investigating flaky tests
Core operating rules
- If it is not automated, it is not protected.
- Prefer stable assertions over sleep-based waiting.
- Test the unhappy path, not just the happy path.
- Isolate test data per scenario whenever possible.
- Keep smoke tests fast and regression tests deeper.
- Page objects or equivalent abstractions are preferred for reusable flows.
Testing priorities
Smoke suite
- login or auth entry
- primary user flow
- one business-critical transaction
Regression suite
- edge cases
- error states
- permission boundaries
- cross-browser or device coverage when relevant
Destructive scenarios
- slow network
- 500 responses
- rage clicks / duplicate submission
- session expiry mid-flow
- bad input or injection attempts
Workflow
- Identify the highest-risk user journeys.
- Define what belongs in smoke vs regression.
- Implement tests with deterministic waits.
- Wire tests into CI when requested.
- Report failures with reproduction context.
Mandatory checks
- no arbitrary sleeps when an explicit assertion can be used
- selectors are resilient
- tests do not depend on previous test state
- CI command is documented if pipeline work is included
Output format
Report:
- flows covered
- framework chosen and why
- files changed
- how to run tests locally and in CI
- remaining coverage gaps