Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
test(pipe-condition): match on the run mode instead of comparing enums
Louis Choquelcf97a474c503
diff --git a/tests/integration/pipelex/pipes/controller/pipe_condition/test_pipe_condition_continue_delivery.py b/tests/integration/pipelex/pipes/controller/pipe_condition/test_pipe_condition_continue_delivery.pyindex 7b44b67ac..930bfc19a 100644--- a/tests/integration/pipelex/pipes/controller/pipe_condition/test_pipe_condition_continue_delivery.py+++ b/tests/integration/pipelex/pipes/controller/pipe_condition/test_pipe_condition_continue_delivery.py@@ -59,7 +59,11 @@ def _make_run_params(run_mode: PipeRunMode) -> PipeRunParams:# The factory is the single writer of the run-mode and fan-out-bound fields, so the fixture goes# through it rather than hand-building params. Assert the mode survived: under a keyless boot the# factory coerces LIVE to DRY, which would silently swap which controller path the test exercises.- assert run_params.run_mode == run_mode, f"This test must run the {run_mode} controller path — the boot coerced it to {run_params.run_mode}"+ match run_mode:+ case PipeRunMode.LIVE:+ assert run_params.run_mode.is_live, f"This test must run the live controller path — the boot coerced it to {run_params.run_mode}"+ case PipeRunMode.DRY:+ assert run_params.run_mode.is_dry, f"This test must run the dry controller path — the boot coerced it to {run_params.run_mode}"return run_params