sscoble/pi-mono
1
0
Fork 0
mirror of https://github.com/badlogic/pi-mono.git synced 2026-11-05 23:37:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

docs(coding-agent): remove issue-specific regression test placement rule (#8775)

Browse source
This commit is contained in:
David Brailovsky 2026-08-28 16:39:28 +02:00 • committed by GitHub
parent 56700d42ed
commit e54d45d119
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 1 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
AGENTS.md
View file

@ -35,7 +35,7 @@
- `packages/tui` (`node:test`): `node --test test/specific.test.ts`
- If you create or modify a test file, run it and iterate on test or implementation until it passes.
- For `packages/coding-agent/test/suite/`, use `test/suite/harness.ts` + the faux provider. No real provider APIs, keys, or paid tokens.
- Put issue-specific regressions under `packages/coding-agent/test/suite/regressions/` named `<issue-number>-<short-slug>.test.ts`.
- When regressions tests for fixing a github issue, add a comment with the github issue number next to the test.
- For ad-hoc scripts, `write` them to a temp file (e.g. `/tmp`), run, edit if needed, remove when done. Don't embed multi-line scripts in `bash` commands.
- Never commit unless the user asks.

6
packages/coding-agent/test/suite/README.md
View file

@ -8,9 +8,3 @@ Rules:
- Do not use real provider APIs, real API keys, network calls, or paid tokens
- Keep these tests CI-safe and deterministic
- Do not use or extend the legacy `test/test-harness.ts` path unless a missing capability forces it
Organization:
- Put broad lifecycle and characterization tests directly under `test/suite/`
- Put issue-specific regression tests under `test/suite/regressions/`
- Name regression tests as `<issue-number>-<short-slug>.test.ts`
- Example: `test/suite/regressions/2023-queued-slash-command-followup.test.ts`