Local web e2e
A curated collection of practical, evidence-backed skills for coding agents.
npx -y skills add zacharygcook/agent-skills --skill local-web-e2eAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Design, run, and debug trustworthy local browser end-to-end tests with isolated ports, disposable data, readiness checks, deterministic seeds, and state restoration. Use for local web smoke suites, authenticated flows, multi-service launchers, or E2E environment hardening.
SKILL.md
2.6 KB, as published. Nobody here has run it
Local Web E2E
Make local browser tests safe to run beside normal development and strong enough to reveal real integration failures.
Safety Invariants
- Use a dedicated E2E database or isolated datastore namespace.
- Fail closed before any reset: verify the target clearly identifies itself as E2E and require an explicit override for exceptions.
- Use dedicated ports and build/cache directories so tests do not collide with running dev servers.
- Never borrow an arbitrary existing server unless the suite verifies its configuration and data target.
- Keep credentials synthetic and secrets out of tracked files.
Environment Lifecycle
- Run a doctor/preflight check for runtimes, browsers, ports, database reachability, and required configuration.
- Build shared packages needed by multiple services.
- Reset, migrate, and seed the disposable datastore deterministically.
- Start services with isolated ports and capture logs.
- Wait on health/readiness endpoints, not fixed sleeps.
- Run browser tests with intentional concurrency.
- On failure, retain traces, screenshots, videos, and service logs.
- Stop only processes launched by the suite and restore mutated state when a test exercises operator controls.
Test Quality
Prefer a short set of high-signal journeys:
- authentication and authorization boundaries;
- a primary user workflow from UI through API and persistence;
- loading, empty, error, and retry states;
- cross-origin/session behavior in realistic local topology;
- admin/operator actions followed by explicit state restoration.
Use stable roles, labels, and test IDs. Avoid timing-only assertions and selectors tied to cosmetic DOM structure. Seed prerequisites directly when setup through the UI would add noise without testing meaningful behavior.
Debugging Order
- Read the first application/service error, not only the browser timeout.
- Confirm the browser reached the intended port and build directory.
- Confirm every service points at the disposable datastore.
- Inspect readiness and seed output.
- Open the trace and screenshot.
- Re-run the narrowest failing test before the whole suite.
Document repository-specific commands and safety sentinels near the launcher. Do not encode one project's ports or package manager into this reusable skill.