From 970455250f884c799a5b59627140bb99d10bc522 Mon Sep 17 00:00:00 2001
From: Mfanafuthi Mhlanga
 <309677444+mfanafuthimhlanga@users.noreply.github.com>
Date: Mon, 3 Aug 2026 21:38:37 +0200
Subject: [PATCH] ci: run buzz-workflow and buzz-acp lib tests in the unit gate
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

`just test-unit` covers buzz-core, buzz-auth, buzz-voice, buzz-cli,
buzz-db --lib, buzz-conformance, buzz-push-gateway, and buzz-backend-kubernetes.
buzz-workflow and buzz-acp are referenced by no `cargo test` or `nextest`
invocation anywhere in .github/workflows/ or scripts/run-tests.sh — buzz-acp
appears only in build and release contexts (Justfile binary loops, sprig.yml).

This is the condition the buzz-backend-kubernetes block immediately above
already names: "nothing in CI runs `cargo test --workspace` — workspace
membership alone buys clippy/check, not a single executed test." Both crates
were enumerated nowhere, so `cargo clippy --workspace --all-targets` compiled
their tests while nothing executed them:

  buzz-workflow --lib    154 tests
  buzz-acp --lib         661 tests

Both are infra-free and pass clean:

  Summary [0.306s] 154 tests run: 154 passed, 2 skipped
  Summary [13.080s] 661 tests run: 661 passed, 0 skipped

buzz-relay is deliberately not addressed here — it needs Postgres, and
api::admin and api::media carry four infra-dependent tests that are not
#[ignore]d, so `-p buzz-relay --lib` hangs ~30s per test and then fails. That
belongs with #3461.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Mfanafuthi Mhlanga <309677444+mfanafuthimhlanga@users.noreply.github.com>
---
 Justfile | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/Justfile b/Justfile
index d6e86c8d099..f5606c2ada5 100644
--- a/Justfile
+++ b/Justfile
@@ -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