fix: split release workflow integration tests to match test.yml structure

Running all tests with `cargo test --test '*'` causes cross-contamination:
OnceLock-based test binaries (comment_tests etc.) leave the bridge running,
and daemon_tests reuses then stops that bridge, leaving subsequent daemon
tests unable to start a fresh bridge ("Could not find project").

Split into separate cargo test invocations matching test.yml groups, with
explicit bridge stops between groups to ensure clean state.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Alexander Kiselev
2026-02-22 16:50:39 -08:00
co-authored by Claude Opus 4.6
parent 6c552b9daa
commit 1614c24f76
+26 -3
View File
@@ -84,9 +84,32 @@ jobs:
- name: Run unit tests
run: cargo test --lib --verbose
- name: Run integration tests
run: cargo test --test '*' --verbose -- --nocapture
timeout-minutes: 80
- name: Run CLI tests
run: cargo test --test e2e --test output_format_integration --verbose
- name: Run read-only integration tests
run: cargo test --test readonly_tests --test command_tests --verbose -- --nocapture
timeout-minutes: 30
env:
RUST_LOG: info
- name: Stop bridge before mutation tests
run: cargo run -- stop --project ci-test || true
shell: bash
- name: Run mutation integration tests
run: cargo test --test comment_tests --test symbol_tests --test patch_tests --test type_tests --test script_tests --verbose -- --nocapture
timeout-minutes: 30
env:
RUST_LOG: info
- name: Stop bridge before infrastructure tests
run: cargo run -- stop --project ci-test || true
shell: bash
- name: Run infrastructure tests
run: cargo test --test daemon_tests --test reliability_tests --test project_tests --verbose -- --nocapture
timeout-minutes: 30
env:
RUST_LOG: info