also looking at this
Implement the web UI server with Zig I/O
#26
8 files
+513
-114
| @@ -105,12 +105,13 @@ This will automatically discover and run all `*.test.zig` files in the `tests` d | ||
| 105 | 105 | - `--shard-index <N>` - Run one one-based file shard |
| 106 | 106 | - `--shard-count <N>` - Set the total number of file shards |
| 107 | 107 | - `--no-color` - Disable color in child Zig test processes |
| 108 | - `--ui` - Serve the live test UI (configure it with `--ui-host` and `--ui-port`) | |
| 108 | 109 | - `--verbose` - Show detailed output |
| 109 | 110 | |
| 110 | 111 | Discovery and programmatic execution share the same test-plan, lifecycle, |
| 111 | 112 | result, and reporter model. Discovery still rejects options it cannot honor |
| 112 | 113 | instead of silently ignoring them: quiet output, parallel jobs, snapshot |
| 113 | updates, memory profiling, and the web UI remain programmatic-only. See | |
| 114 | updates, and memory profiling remain programmatic-only. See | |
| 114 | 115 | [the execution pipeline architecture](docs/execution-pipeline.md) for extension |
| 115 | 116 | points, timeout semantics, and migration guidance. |
| 116 | 117 | |
| @@ -129,6 +130,9 @@ zig-test --test-dir tests --no-recursive | ||
| 129 | 130 | # Stop on first failure |
| 130 | 131 | zig-test --test-dir tests --bail |
| 131 | 132 | |
| 133 | # Watch tests in the live web UI | |
| 134 | zig-test --test-dir tests --ui --watch | |
| 135 | ||
| 132 | 136 | # Retry failures twice and fail CI if any test is flaky |
| 133 | 137 | zig-test --test-dir tests --retry 2 --fail-on-flaky |
| 134 | 138 | |