adk

func BuildBinaries ¶

func BuildBinaries() (func(), error)

BuildBinaries compiles gapid and gapictl into a directory the suite owns, and returns a function that removes it.

GAPI-DIV-097: this suite shells out to both binaries, and before this existed it did not produce either of them. The absence check in gapictlPath fails loudly when bin/gapictl is missing, which made the harness look guarded while nothing at all detected a STALE binary - the common case for a developer who edits pkg/cli and runs the suite. A bin/gapictl a day older than the change under test produced `ok github.com/goppydae/gapi/test/adk 191.263s`, an entirely green run against the previous binary, over four subtests that failed immediately after `mage build`. CI was immune only because its workflow builds first; the local run typed the same command in the wrong sequence.

Building rather than asserting freshness removes the failure mode instead of reporting it, and makes `go test ./test/adk/` correct on its own - which is what a developer will type.

The binaries are NOT written to the checkout's bin/. A suite that overwrote the operator's build would make its own correctness a side effect on someone else's artifact, and `mage build` and this suite would race whenever both ran.

No version ldflags are passed. mage's Build stamps them; nothing here reads a version, and a test that needed one would be asserting on the build system rather than on the code.