Module dev_run 

#2138 (end-to-end testing track §3.5): bynk test --against dev, the system suites run against a local bynk dev the runner starts itself.

For each distinct env the system cases run with (one group), this:

1. starts bynk dev --ready-json (local wrangler dev/workerd only, never -- --remote) with the group’s env and a fixed test value for every other secret the Workers declare, passed as -- --var NAME:VALUE;
2. waits for the readiness file, whose URLs must all be loopback;
3. runs the group’s cases against those URLs (this binary again, with crate::remote::DEV_URLS_ENV and crate::remote::DEV_ENV_ENV), signing with the same secret values;
4. stops bynk dev by its own pid (it stops its wranglers and their workerds), then its process group if anything is left.

Groups run in turn; their results are reported together.

Structs

DevRunArgs

What the orchestration needs from the test invocation.

Constants

TEST_SECRET

The value every declared secret the case doesn’t set takes, both in the Workers (-- --var) and in the runner that signs for them.

Functions

dev_vars

The variables one bynk dev serves: the group’s env, then each declared secret the group doesn’t set at the fixed test value.

remove_stale

Remove a readiness file left by an earlier run, so it is never read as this session being ready. A missing file is fine.

run

Run every system suite against a local bynk dev, one per distinct env.