(iggy) branch master updated: docs(integration): say that the test harness runs prebuilt binaries (#4160)

[pi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

spetz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/iggy.git


The following commit(s) were added to refs/heads/master by this push:
     new 9a4fd0f75 docs(integration): say that the test harness runs prebuilt binaries (#4160)
9a4fd0f75 is described below

commit 9a4fd0f754c3b699354826b177e0a7a113f0a03e
Author: Maxim Levkov <ml...@users.noreply.github.com>
AuthorDate: Sat Sep 12 14:17:51 2026 -0700

    docs(integration): say that the test harness runs prebuilt binaries (#4160)
    
    Closes #4159.
---
 AGENTS.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/AGENTS.md b/AGENTS.md
index ada37f145..f3f3ce423 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -188,9 +188,11 @@ non-trivial change passes verification, suggest `/team-review <target>`.
 
 BDD test naming: `given_X_when_Y_should_Z` (3-part). Promote to 4-part `given_X_when_Y_then_Z_should_W` only with a distinct "then" intermediate. Be consistent inside a file.
 
-Filter a single integration test by path:
+Filter a single integration test by path. Build the binaries the harness launches first: it runs
+whatever is already in `target/`, so a stale one fails as though the change under test broke it.
 
 ```bash
+cargo build --bin iggy-server --bin iggy-connectors
 cargo test -p integration -- connectors::runtime::benchmark::given_logging_format_json
 ```
 
@@ -202,6 +204,7 @@ cargo test -p integration -- connectors::runtime::benchmark::given_logging_forma
 - **`test_logs/` grows quickly.** Wipe between major refactors.
 - **Miri only covers `binary_protocol` + `consensus`.** Cannot emulate `io_uring` syscalls. do not try to expand Miri to crates that pull `compio`.
 - **Integration crate has no `--test` target.** Filter by test path inside the single `mod.rs` binary.
+- **The integration harness runs prebuilt binaries and never builds them.** `Command::cargo_bin` only resolves a path, so a stale `iggy-server`, `iggy-connectors` or `iggy-mcp` is used silently. CI builds first (`cargo build --locked --bin iggy-server --bin iggy`); a local run does not, and a stale binary fails in ways that look like the change under test. Rebuild after anything that touches a launched binary or its config.
 
 ## Local state directories