Agmente / AgmenteUITests
AGENTS.md545 starsChanged 9 months agoMITView on GitHub
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- ACPClient/AGENTS.mdAGENTS.md
- Agents.mdAGENTS.md
- Agmente/AGENTS.mdAGENTS.md
- AgmenteTests/AGENTS.mdAGENTS.md
- AppServerClient/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- acp-local-runnerSkill
- codex-local-cli-e2eSkill
- repeat-with-delaySkill
- upstream-protocol-drift-watchSkill
- run-agmente-codex-e2eSkill
- run-agmente-e2eSkill
The file
We split this AGENTS.md into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Use root .agmente.paths for machine-local ACP/Codex checkout locations when debugging upstream compatibility.
- Distinctive: line 8
Read it as the source of truth.
- Distinctive: line 11
Add-server flows for ACP and Codex.
- Distinctive: line 25
Do not hard-code developer-specific endpoints or filesystem paths in tests.
- Distinctive: line 28
Prefer accessibility IDs over coordinate taps.
- Distinctive: line 29
If adding/changing critical controls, add stable accessibility IDs in app code.
- Distinctive: line 30
Keep ACP and Codex add-server flows separately validated.
- Distinctive: line 31
Keep test assertions tied to behavior, not layout coordinates.
- Distinctive: line 34
After simulator E2E runs:
- Distinctive: line 35
Stop local agent/app-server process.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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
Agmente UI Tests Guide
Scope
Simulator-driven UI tests, including scenario-backed manual E2E and opt-in Codex local E2E.
External Repo Paths
- Use root
.agmente.pathsfor machine-local ACP/Codex checkout locations when debugging upstream compatibility. - Read it as the source of truth; do not hard-code local absolute paths.
Coverage Goals
- Add-server flows for ACP and Codex.
- Connect/initialize/session lifecycle UX.
- Prompt send/stream/render experience.
- Accessibility-id stability for critical controls.
Codex E2E Contract
- E2E test is opt-in and environment-driven.
- Scenario intent lives under
e2e/scenarios/codex/; the env vars below are the UI-test harness contract, not the source of truth for scenario behavior. - Supported env keys:
AGMENTE_E2E_CODEX_ENABLEDAGMENTE_E2E_CODEX_ENDPOINTAGMENTE_E2E_CODEX_HOSTAGMENTE_E2E_CODEX_PROMPTAGMENTE_E2E_CODEX_CONFIG_PATH
- Do not hard-code developer-specific endpoints or filesystem paths in tests.
UI Automation Rules
- Prefer accessibility IDs over coordinate taps.
- If adding/changing critical controls, add stable accessibility IDs in app code.
- Keep ACP and Codex add-server flows separately validated.
- Keep test assertions tied to behavior, not layout coordinates.
Cleanup Expectations
After simulator E2E runs:
- Stop local agent/app-server process.
- Uninstall app from simulator to reset state.
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.

