Homebrew Formula Test Block: Client–Server Integration Without Production Credentials

When a Homebrew formula contains a client binary that depends on a local server binary, the test do ... end block is the only documented way to validate that the two components interoperate without touching any production systems. The test runs in a sandboxed testpath, using only locally built artifacts and throwaway files, so any network activity must be confined to the loopback interface.

Developers often need to know whether the sandbox permits binding to a loopback port for a client–server handshake, whether the test harness automatically starts the dependency server, and how these behaviors vary across Homebrew releases and between macOS and Linux CI environments.

Unresolved questions include:

• Does the Homebrew test sandbox allow a client process to bind to a loopback socket for an integration check?
• Are there differences in this capability between recent Homebrew releases (e.g., 4.x vs. 3.x) or between macOS and Linux?
• When using brew test-bot, does it automatically launch dependency services required by the test block, or must the test manually start them?