e2e-debugging
Skill16 starsChanged 25 days agoMITView on GitHub
Debug Azents E2E tests, fixtures, browser state, and local integration failures.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/conventions/AGENTS.mdAGENTS.md
- python/AGENTS.mdAGENTS.md
- swift/AGENTS.mdAGENTS.md
- typescript/AGENTS.mdAGENTS.md
- .claude/conventions/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- python/CLAUDE.mdCLAUDE.md
- swift/CLAUDE.mdCLAUDE.md
- typescript/CLAUDE.mdCLAUDE.md
- add-conventionSkill
- ci-optimizationSkill
- code-reviewSkill
- convention-auditSkill
- create-prSkill
- dependabot-alertsSkill
- frontend-designSkill
- github-markdown-bodiesSkill
- living-spec-auditSkill
- openapi-client-genSkill
- python-dependency-managementSkill
- python-dependency-tree-analysisSkill
- python-dependency-updateSkill
- python-quality-checkSkill
- ship-featureSkill
- ship-prSkill
- skill-creatorSkill
- spec-reviewSkill
- stacked-prsSkill
- technical-feature-designSkill
- typescript-dependency-tree-analysisSkill
- typescript-dependency-updateSkill
- typescript-quality-checkSkill
- ui-visual-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Run a focused test:
- Distinctive: line 38
Check fixture readiness before changing product code.
- Distinctive: line 40
Prefer adding or updating E2E coverage for product behavior verification.
- Distinctive: line 46
Do not write product verification as legacy setup scripts.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Azents E2E Debugging
Azents E2E tests live under testenv/azents/e2e/.
Common Commands
cd testenv/azents/e2e
uv run pytest ./src -vRun a focused test:
cd testenv/azents/e2e
uv run pytest ./src/tests/azents/public/test_health.py -v -sFixture Preparation
cd testenv/azents
uv run testenv bootstrap local
uv run testenv prerequisite prepare --profile live --json
uv run testenv fixture doctor <fixture-id> --json
uv run testenv fixture up <fixture-id> --jsonDebugging Pattern
- Reproduce with the smallest E2E test selection.
- Capture server logs and browser traces when available.
- Check fixture readiness before changing product code.
- Fix fixture support only when the product behavior is already correct.
- Prefer adding or updating E2E coverage for product behavior verification.
Notes
- E2E tests may require Docker.
- Live/external tests require prepared prerequisite snapshots.
- Do not write product verification as legacy setup scripts; use E2E tests as the primary verification layer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

