Docs and guard rails: GitHub Pages only, where code goes, updated skills
- docs/adr/0001: GitHub Pages is the only host, not open for renegotiation - docs/adr/0002: source in many files, shipped as one page assembled at build - tests/pages.test.js: builds stay static files Pages can serve, all local references resolve, only release.yml deploys and only via the Pages actions - tests/build.test.js: partial naming and layout rules - new skills: github-pages, edit-the-game; add-strings, performance, release and write-tests updated for src/, sorted dictionaries and --base-ref - CLAUDE.md, ARCHITECTURE.md, CONTRIBUTING.md (incl. porting older branches), README.md and the PR template describe the new layout
This commit is contained in:
parent
052fdd713f
commit
05ff4ea7ad
15 changed files with 530 additions and 101 deletions
|
|
@ -5,8 +5,8 @@ description: Write deterministic jsdom tests for Series of Tubes features and fi
|
|||
|
||||
# Writing tests
|
||||
|
||||
Tests use `node:test` and `tests/harness.js`, which loads `site/index.html` in jsdom
|
||||
with the animation loop off, a seeded `Math.random` and a recording fake canvas.
|
||||
Tests use `node:test` and `tests/harness.js`, which assembles the game page from `src/`
|
||||
(once per test file) and loads it in jsdom with the animation loop off, a seeded `Math.random` and a recording fake canvas.
|
||||
Code runs inside the page through `ev()`.
|
||||
|
||||
## Pattern
|
||||
|
|
@ -29,8 +29,11 @@ test('what the player should see happen', () => {
|
|||
|
||||
Pick the suite by topic: `game` (core loop), `build`, `persist` (save/import/migrate),
|
||||
`services` (customers), `peering`, `issues` (GitHub issue regressions, name them
|
||||
`#NN …`), `regions`, `modes` (scenarios, sandbox, weekly), `i18n`. A new file must be
|
||||
added to the `test` script in `package.json`.
|
||||
`#NN …`), `regions`, `modes` (scenarios, sandbox, weekly), `i18n`, `pages` (hosting).
|
||||
For a new feature, prefer a new file named after it (`tests/route-servers.test.js`): every
|
||||
`tests/*.test.js` runs on its own (`scripts/test.js`), and a file of your own never conflicts
|
||||
with someone else's tests. Appending to the big suites (`issues`, `regions`) is where
|
||||
pull requests collide. Run one file with `npm test -- tests/route-servers.test.js`.
|
||||
|
||||
## Rules
|
||||
|
||||
|
|
@ -40,7 +43,7 @@ added to the `test` script in `package.json`.
|
|||
```js
|
||||
ev("eval('('+fireFailure.toString().replace('const e=pick(opts);',\"const e='crash';\")+')')()");
|
||||
```
|
||||
Check the current source for the exact `pick` line first; it may differ.
|
||||
Check the current source for the exact `pick` line first (`grep -rn "function fireFailure" src/game`); it may differ.
|
||||
- **Drive the game through `ACT`** like a player would, then `compute()` or `dayTick()`.
|
||||
- **Saves:** for persistence changes, round-trip `JSON.stringify(S)` through
|
||||
`parseSave()`/`migrate()`, and test that an *old* save without the new field still loads.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue