Skip to content

Read the run counts node:test writes - #137

Merged
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:ci/node-test-dialect
Sep 8, 2026
Merged

Read the run counts node:test writes#137
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:ci/node-test-dialect

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

node --test is the sixth dialect, and it differs from the other five in
counting the tests that never ran in TWO places. A run of two passing, one
skipped and one deferred prints tests 4, pass 2, skipped 1, todo 1: the
two not-run counters are disjoint from pass and from each other, so a reader
watching skipped alone certifies a suite whose every remaining test is
deferred. Node prints a deferred test with a tick, which is the "reads as a
pass" shape this tool exists to refuse, so both counters sum into the skip
count.

It is read before pytest for the reason Catch2 is: a log carries whatever else
the job printed, and a phrase shaped like pytest's summary sitting beside node's
counters would otherwise decide the total. A test holds that order.

Every string in the three new tests is copied from a real node --test run.
Against one, the tool reads total=4 skipped=2 and exits 1 naming two skipped
tests; against a clean run it reads total=2 skipped=0 and exits 0. 21 tests
pass.

`node --test` is the sixth dialect, and it differs from the other five in
counting the tests that never ran in TWO places. A run of two passing, one
skipped and one deferred prints `tests 4`, `pass 2`, `skipped 1`, `todo 1`: the
two not-run counters are disjoint from `pass` and from each other, so a reader
watching `skipped` alone certifies a suite whose every remaining test is
deferred. Node prints a deferred test with a tick, which is the "reads as a
pass" shape this tool exists to refuse, so both counters sum into the skip
count.

It is read before pytest for the reason Catch2 is: a log carries whatever else
the job printed, and a phrase shaped like pytest's summary sitting beside node's
counters would otherwise decide the total. A test holds that order.

Every string in the three new tests is copied from a real `node --test` run.
Against one, the tool reads `total=4 skipped=2` and exits 1 naming two skipped
tests; against a clean run it reads `total=2 skipped=0` and exits 0. 21 tests
pass.
@estebanzimanyi
estebanzimanyi merged commit 96aea5d into MobilityDB:master Sep 8, 2026
2 checks passed
@estebanzimanyi
estebanzimanyi deleted the ci/node-test-dialect branch September 8, 2026 01:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant