e2e-testing

Files (2)

• SKILL.md
• SKILL.md.lock

SKILL.md (first lines)

<!-- bodyRef: skills/sources/e2e-testing.md -->

<!-- Generated by `harness skills bootstrap`. Edit to tune; re-run to regenerate. -->
<!-- Static skills point at live docs by design — do not hardwire version-pinned API here. -->

Use this skill when writing end-to-end tests for critical user or system flows.

## Concepts (timeless)
- E2E covers the real entry point a user/operator hits — not a private helper. If a flow matters, it gets an e2e test.
- Keep them few and high-value: critical paths (auth, checkout, primary CRUD), not every permutation.
- Make them deterministic: seed/reset state, wait on conditions (not sleeps), isolate test data.
- Treat flakiness as a bug — quarantine and fix, don't retry-until-green blindly.

## Pull current docs first
Browser/automation tooling moves fast — confirm the current API and selectors guidance:
- your e2e runner's current setup + assertion API
- For browser flows, prefer the project's chosen runner; verify its current setup + assertion API.

## Checklist
- [ ] Critical flows exercised through the real entry point
- [ ] Deterministic setup/teardown; condition-based waits, no fixed sleeps
- [ ] Test data isolated; no cross-test coupling
- [ ] Failures are actionable (clear assertion + artifact on failure)
- [ ] Flaky tests fixed or quarantined, never silently retried

## Gotchas

_Highest-signal section. Seed empty; grow it from real failures this skill
hits — `harness skills propose` suggests entries here from drift evidence._

- _none observed yet_

From ichiorca/shipsignal, Apache-2.0.

More from ichiorca/shipsignal