You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
barrage has no equivalent to pytest's `parametrize`. Open-code that with
`do_test_*(params...)` helpers and individual tests calling that.
Stop passing the explicit `--distribution` to the test. The new
`ImageConfigManager` singleton (which replaces the old `config` pytest
fixture) reads the distribution from `mkosi.local.conf`. This avoids
having to specify it twice, and leaves the configuration to
`integration-test-setup.sh`.
Drop the `log_setup()` call. The integration tests themselves don't use
`logging`, this mostly just affects the called `mkosi` subprocesses
which already do it. This is very prone to interfere with barrage's own
stderr capturing.
Replace the `--debug-shell` pytest option with a `TEST_DEBUG_SHELL` env
variable, as barrage doesn't have test-defined CLI options.
Make the mkosi invocations in tests/__init__.py async, so that they can
actually run in parallel.
Remove installation and remaining traces of pytest.
Co-developed-by: Claude Opus 4.8 <noreply@anthropic.com>
-`python3 -m pytest -m integration ...` to run integration tests. No need to run these by default.
20
+
-`bin/mkosi box -- python3 -m barrage --pattern 'integration_*.py' tests/` to run integration tests (after `tools/integration-test-setup.sh`). No need to run these by default.
21
21
-`bin/mkosi box -- python3 -m barrage --pattern 'install_*.py'` to run installation tests (venv/pip/zipapp). Skipped by default as they install from the network. No need to run these by default.
22
-
23
22
- Never invent your own build commands or try to optimize the build process.
24
23
- Never use `head`, `tail`, or pipe (`|`) the output of build or test commands. Always let the full output
25
24
display. This is critical for diagnosing build and test failures.
0 commit comments