agentic-identity-broker / tests
AGENTS.md68 starsChanged 10 days agoMITView on GitHub
All paths in this file are relative to the repository root. Run commands from the repository root. Read the changed tests and the nearest suite instructions before you write a test. Before you change behavior, read the governing feature's spec.md, plan.md, and tasks.md under specs/. For HTTP assertions, read the relevant operation in api/enduser/openapi.yaml or api/admin/openapi.yaml. ExtProc agentgateway E2E tests and the backend agentgateway scenario use Docker. Infra-backed integration tests use PostgreSQL and an AWS emulator. They require Docker or…
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 31,700 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 repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- infra/AGENTS.mdAGENTS.md
- internal/AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- infra/CLAUDE.mdCLAUDE.md
- internal/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- web/CLAUDE.mdCLAUDE.md
- agents-md-housekeepingSkill
- aws-crypto-goSkill
- jwx-guide-v4Skill
- simple-englishSkill
- speckit-agent-context-updateSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- speckit-agent-context-updateSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- agentic-workflowsSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
All paths in this file are relative to the repository root.
- Distinctive: line 5
Read the changed tests and the nearest suite instructions before you write a test.
- Very specific: line 19
Before you change behavior, read the governing feature's spec.md, plan.md, and tasks.md under specs/.
- Distinctive: line 40
Keep self-contained tests free of container dependencies.
- Distinctive: line 42
Do not add browser or screenshot work to non-frontend suites.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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
Tests (tests/)
All paths in this file are relative to the repository root. Run commands from the repository root.
Read the changed tests and the nearest suite instructions before you write a test.
Read First
| Source | Purpose |
.specify/memory/constitution.md — Principles VIII and XIII | Test-first delivery, semantic failures, acceptance coverage |
ARCHITECTURE.md — End-to-End Testing Architecture | Stable scenarios and production bootstrap |
adrs/007-e2e-testing-with-ginkgo.md | Accepted E2E architecture |
tests/e2e/AGENTS.md | Broker HTTP and ExtProc E2E rules |
tests/e2e/frontend/AGENTS.md | Browser lifecycle, page objects, screenshots |
tests/integration/AGENTS.md | Component tests, infrastructure helpers, commands |
justfile | Suite boundaries, worker counts, report recipes |
Before you change behavior, read the governing feature's spec.md, plan.md, and tasks.md under specs/.
For HTTP assertions, read the relevant operation in api/enduser/openapi.yaml or api/admin/openapi.yaml.
ExtProc agentgateway E2E tests and the backend agentgateway scenario use Docker. Infra-backed integration tests use PostgreSQL and an AWS emulator. They require Docker or Podman.
Choose the Suite
| Suite | Framework | Scope | Infrastructure | Command |
tests/e2e/ | Ginkgo v2 / Gomega | Broker HTTP acceptance scenarios | Production bootstrap, normally in-memory storage | just test-e2e-backend |
Docker-tagged tests/e2e/ scenarios | Ginkgo v2 / Gomega | Agentgateway policy acceptance | Production broker and agentgateway container | just test-e2e-docker |
tests/e2e/extproc/ | Ginkgo v2 / Gomega | ExtProc acceptance scenarios | Some agentgateway scenarios require Docker | just test-e2e-extproc |
tests/e2e/frontend/ | Ginkgo v2 / Playwright Go | Browser acceptance scenarios | Built frontend and Chromium | just test-e2e-frontend |
tests/integration/ | Standard go test / testify assertions | Component behavior and configuration | Self-contained by default | just test-integration |
| Tagged integration packages | Standard go test / testify assertions | PostgreSQL, migrations, encryption | PostgreSQL and AWS emulator containers | just test-integration-infra |
just test excludes E2E and integration suites.
just test-e2e runs the backend, Docker-tagged backend, ExtProc, and frontend recipes.
just test-integration-all runs both integration layers.
Keep self-contained tests free of container dependencies. Retain real infrastructure coverage for behavior that depends on PostgreSQL, KMS, or DynamoDB. Do not add browser or screenshot work to non-frontend suites.
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.