jochen 8635560993 A suite run in which no test passed exits non-zero and names its skips (issue 693) ...

The runner exits 0 when every test skipped, so a bed that stopped before its
subject and skipped its only test as NOT REACHED was recorded as passed, "0
passed, 0 failed". The suite now collects each skip and its reason through a
reporter of its own, prints NOT PASSED and a skipped line per skip after its
recorded line, keeps them in the receipt, and exits 1 when no test passed or a
test was not reached. A skip for a declared reason beside passes stays passed.

2026-10-14 03:14:05 +02:00

..

integration

Let a bed's forge take the lab's shallow checkouts (issue 689)

2026-10-14 02:21:21 +02:00

beds-read-the-catalogue.test.ts

A cache consumer presents the login it was granted, checked over the catalogue; the two-node bed's baserow keeps its own cache and the bed asserts it answers (issue 081)

2026-09-22 12:26:34 +02:00

bus-kept.test.ts

Raise genesis past its broker step and hold that the bus is kept (hq issue 590, ADR 0333 §5)

2026-10-13 02:13:35 +02:00

cache-consumers-present-their-login.test.ts

Review of 081: the bed asserts baserow chose its own cache and it challenges for its password; the check reads only what a module hands its software; stale comments

2026-09-22 12:34:59 +02:00

catalogue-module.test.ts

The lab stands in for the builder on an upstream artifact too: the reference the manifest pins

2026-09-21 22:33:44 +02:00

connect.test.ts

Reach one scenario from the workstation, by name

2026-09-01 16:42:26 +02:00

diagram.test.ts

The home segment moves off 192.168.1.0/24

2026-09-11 00:00:19 +02:00

egress-routes.test.ts

The home segment moves off 192.168.1.0/24

2026-09-11 00:00:19 +02:00

enumerate.test.ts

Inject the incus command, so the enumeration tests fail incus on every machine

2026-10-08 10:15:59 +02:00

forge.test.ts

Let a bed's forge take the lab's shallow checkouts (issue 689)

2026-10-14 02:21:21 +02:00

invariants.test.ts

The home segment moves off 192.168.1.0/24

2026-09-11 00:00:19 +02:00

lastrun.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

log.test.ts

Say what the lab is doing, while it is doing it

2026-09-01 10:43:38 +02:00

names.test.ts

Scenario lifecycle: raise, exec, snapshot, restore, destroy

2026-08-24 01:12:49 +02:00

net.test.ts

Scenario lifecycle: raise, exec, snapshot, restore, destroy

2026-08-24 01:12:49 +02:00

outcomes.test.ts

A suite run in which no test passed exits non-zero and names its skips (issue 693)

2026-10-14 03:14:05 +02:00

pinning.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

place.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

rebuild.test.ts

The receipt claims the catalogue the beds read

2026-09-21 14:14:54 +02:00

router.test.ts

The home segment moves off 192.168.1.0/24

2026-09-11 00:00:19 +02:00

runtimes.test.ts

The run rebuilds the module runtimes its beds stock

2026-09-21 19:26:59 +02:00

suite.test.ts

A suite run in which no test passed exits non-zero and names its skips (issue 693)

2026-10-14 03:14:05 +02:00

supported.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

uplink.test.ts

Prove a machine joins through the tunnel in a bed of its own

2026-10-08 01:52:58 +02:00

validate.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

warm.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00