stoa-platformstoa-platform/stoa/e2e/CLAUDE.md

stoa / e2e

CLAUDE.md9 starsChanged 7 months agoApache-2.0View on GitHub

Détail on-demand: .claude/docs/e2e-audit.md, testing-standards.md.

In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- control-plane-api/CLAUDE.mdCLAUDE.md
- control-plane-ui/CLAUDE.mdCLAUDE.md
- portal/CLAUDE.mdCLAUDE.md
- stoa-gateway/CLAUDE.mdCLAUDE.md
- analyticsSkill
- cartoSkill
- ci-debugSkill
- ci-fixSkill
- competitive-watchSkill
- councilSkill
- decomposeSkill
- extractSkill
- fill-cycleSkill
- generate-backlogSkill
- impactSkill
- memory-consolidateSkill
- monitor-cdSkill
- parallel-reviewSkill
- pr-guardianSkill
- rewriteSkill
- roadmapSkill
- spec-drivenSkill
- sync-planSkill
- verify-megaSkill

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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:
Depends on: All running services (Portal, Console, API, Gateway, Keycloak)
line 44

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

CLAUDE.md

E2E Tests

Overview

Playwright + BDD end-to-end tests with Gherkin feature files. Covers Portal, Console, Gateway, and TTFTC (Time to First Tool Call) scenarios.

Tech Stack

Playwright 1.48, playwright-bdd 7.4, TypeScript
Gherkin .feature files as source of truth

Test Projects

Project	Base URL	Auth	Tests
auth-setup	—	Keycloak login	fixtures/auth.setup.ts
portal-chromium	STOA_PORTAL_URL	parzival state	features/portal-*
console-chromium	STOA_CONSOLE_URL	parzival state	features/console-*
gateway	STOA_GATEWAY_URL	API keys	features/gateway-*
ttftc	STOA_PORTAL_URL	fresh (alex)	features/alex-ttftc

Personas (Ready Player One theme)

Persona	Tenant	Role	Default App
parzival	high-five	tenant-admin	console
art3mis	high-five	devops	portal
aech	high-five	viewer	portal
sorrento	ioi	tenant-admin	console
i-r0k	ioi	viewer	portal
anorak	* (all)	cpi-admin	console
alex	oasis	viewer	portal

Commands

npm run test:e2e       # Full suite
npm run test:smoke     # @smoke only
npm run test:critical  # @critical only
npm run test:portal    # @portal only
npm run test:console   # @console only
npm run test:gateway   # @gateway only
npm run test:demo      # @demo only

Dependencies

Depends on: All running services (Portal, Console, API, Gateway, Keycloak)
See .claude/skills/e2e-test.md for detailed patterns and step definitions

Règles

Détail on-demand: .claude/docs/e2e-audit.md, testing-standards.md.

Audits → docs/audits/YYYY-MM-DD-<topic>/ avec README.md + report/index.html + results.json.
Pas de skips. Si blocage → fix le blocker, pas le test.
Pas de fake data. Toute valeur affichée dans un dashboard vient d'une action phase précédente.
Screenshots = assertions. fullPage: true, naming trace-<app>-<page>.png.
Cross-validation obligatoire: Phase D query l'API et assert counts == actions phases précédentes.
Idempotent: tests runnable N fois sans cleanup. Timestamps dans names, handle 409.
@regression tag sur scénarios bloquant des fixes (regression-guard.yml).
Feature/fix ticket MUST update Playwright scenarios dans la MÊME PR. Pas de "test later".
Evidence archive après CHAQUE run: docs/audits/<date>-<topic>/. Pas d'archive = session incomplète.
data-testid convention: <section>-<element>[-<variant>]. Suffixes -count/-timestamp/-duration auto-masked.
axe-core threshold: critical (WCAG 2.1 AA). Nouvelle page Console → ajouter à CONSOLE_PAGES.
Visual regression: golden baselines dans e2e/golden/. Regen via Docker (voir docs).

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free