This is a Shiplight E2E test project.
Project Layout
specs/tests/ one Markdown spec per executable test
tests/ executable Shiplight YAML tests
environments/ environment files (name → base URL)
auth/ auth fixture TypeScript files, if any
templates/ reusable YAML statement groups, if any
functions/ TypeScript helper functions, if any
files/ fixture files, if any
test-results/ generated runtime artifacts (do not edit)
shiplight-report/ generated reports (do not edit)
.shiplight/ local Shiplight state (do not edit)
Edit Contract
Agents may edit:
specs/tests/**/*.mdtests/**/*.test.yamlenvironments/**/*.env.yamlauth/**/*.auth.tstemplates/**/*.tmpl.yamlfunctions/**/*.func.tsfiles/**playwright.config.ts— only when changing project-level runtime behaviorpackage.json— only when changing commands or dependencies
Agents must not edit:
**/*.yaml.spec.tstest-results/**shiplight-report/**.shiplight/**node_modules/**.envpackage-lock.json— unless a dependency change requires it
Commands
npm test # run all tests
npm run test:headed # run all tests headed
Use the narrowest relevant command when debugging a specific test.
Ground Truth
When sources disagree, this precedence applies:
- Explicit user instruction
- Test spec in
specs/tests/ - Existing test
goal, stepintent, andVERIFYassertions - Current app behavior
- Agent docs in this project
- Agent inference
If current app behavior conflicts with the test spec or test goal, report the mismatch — do not silently rewrite the test.
On every invocation
- Read
references/knowledge.md— how to read and write knowledge notes. - Check
knowledge/in the current working directory for runtime knowledge notes left by previous agents. Read any files relevant to your task.
Task-specific guides
Read the guide(s) that match your task before proceeding:
| Task | Guides |
|---|---|
| Writing a new test | references/creating-tests.md, references/test-design-guide.md, references/test-implementation-guide.md |
| Updating or fixing a test | references/updating-tests.md, references/test-design-guide.md, references/test-implementation-guide.md |
| Auth fixtures and login | references/auth.md |
After reading
Confirm to the user which guides you loaded, then proceed with the task.