Skip to content

ci: run buzz-workflow and buzz-acp lib tests in the unit gate #4590

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mfanafuthimhlanga wants to merge 1 commit into
base: main
Choose a base branch
from
Open

ci: run buzz-workflow and buzz-acp lib tests in the unit gate #4590

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions Justfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -307,6 +307,15 @@ test-unit:
# because nothing in CI runs `cargo test --workspace` — workspace
# membership alone buys clippy/check, not a single executed test.
cargo nextest run -p buzz-backend-kubernetes
# Same reason as the block above: workspace membership buys clippy and
# check, not an executed test. buzz-workflow (schema, executor) and
# buzz-acp (queue, pool, subscriptions) were referenced by no cargo test
# or nextest invocation anywhere, so their lib tests compiled and never
# ran. Both are infra-free — the Postgres-backed cases are #[ignore]d,
# which nextest skips by default. buzz-relay is not added here: it needs
# Postgres and carries four non-#[ignore]d infra-dependent tests. See #3461.
cargo nextest run -p buzz-workflow --lib
cargo nextest run -p buzz-acp --lib
else
./scripts/run-tests.sh unit
fi
Expand Down