- The harness builds the DOM without the page's 2 MB of script text and
runs the scripts straight in the window: a page load in tests takes
about half the time (jsdom's parser was slow on the script text).
- That also took the game's source out of the DOM, which showed three
tests that matched a phrase in the page source rather than the screen;
they now check the panel, the routing window and the dictionary.
- CI plans its split once and runs the tests on 6 runners; every run on
main records each file's time and caches it, so the parts stay even
without anyone refreshing tests/durations.json.
- auto-release.yml and release.yml call the same sharded tests instead
of running all 170 files on one runner each (11 and 15 min); a release
is tested once, before it is tagged.
- Audit: five tests that duplicated a gameplay rule or checked nothing
are gone; the two slowest checks sample a third of the cities, and a
year of play to reach one due date became a moved due date.
npm test ran every file one after another (--test-concurrency=1, from when there were three files). It now runs as many files at once as there are cores (TEST_JOBS=1 for the old way), and --shard i/n picks one of n parts of about equal time, balanced by tests/durations.json (npm run test:timings). CI runs four parts and the build side by side; a final 'test' job is green only when all are, so the check keeps its name. A newer push to a PR cancels the older run.