feat(test): simplify macOS testing with automatic cross-compilation

[mlwelles]

Summary

This PR eliminates manual setup for running integration tests on macOS and introduces a unified test interface via Make.

Key Features

1. Automatic Cross-Compilation (macOS)

Previously, macOS developers had to manually cross-compile a Linux binary and juggle environment variables. Now, make install handles everything automatically.

2. Unified Test Interface

A single make test entry point that routes to the appropriate test runner based on variables:

# Run all tests (default)
make test

# Use variables to control what runs
make test SUITE=systest              # Run systest suite via t/ runner
make test TAGS=integration2          # Run integration2 tests via go test
make test FUZZ=1 PKG=dql             # Fuzz test the dql package
make test TAGS=upgrade PKG=acl       # Run ACL upgrade tests

3. Convenient Shortcuts

Every SUITE and TAGS value has a corresponding helper target:

# SUITE-based targets
make test-all           # All test suites (i.e. 'make test SUITE=all')
make test-unit          # Unit tests, no Docker (i.e. 'make test SUITE=unit')
make test-core          # Core tests (i.e. 'make test SUITE=core')
make test-systest       # System integration tests (i.e. 'make test SUITE=systest')
make test-vector        # Vector search tests (i.e. 'make test SUITE=vector')
make test-ldbc          # LDBC benchmark tests (i.e. 'make test SUITE=ldbc')
make test-load          # Heavy load tests (i.e. 'make test SUITE=load')

# TAGS-based targets
make test-integration   # Integration tests (i.e. 'make test TAGS=integration')
make test-integration2  # Integration2 tests (i.e. 'make test TAGS=integration2')
make test-upgrade       # Upgrade tests (i.e. 'make test TAGS=upgrade')

# Other
make test-fuzz          # Fuzz tests (i.e. 'make test FUZZ=1')
make test-benchmark PKG=posting  # Benchmark a specific package

4. Dynamic Discovery

make help dynamically discovers available SUITE values from t/t.go and TAGS values from test file build directives.

Changes

• Build automation: make install auto-detects the OS and builds both native and Linux binaries on non-Linux systems
• Unified test target: make test routes to t/ runner or go test based on SUITE, TAGS, FUZZ variables
• Complete helper targets: Every SUITE and TAGS value has a corresponding test-* target
• Dynamic help: make help shows available SUITE/TAGS values discovered from the codebase
• Environment variable: Introduced LINUX_GOBIN to specify where Linux binaries are stored for Docker tests
• Docker compose: All systest docker-compose files updated to use ${LINUX_GOBIN:-$GOPATH/bin} for binary mounting
• Documentation: Updated TESTING.md, CONTRIBUTING.md with comprehensive examples

Before (macOS)

make install
mv $GOPATH/bin/dgraph $GOPATH/bin/dgraph_osx
GOOS=linux make install
mv $GOPATH/bin/linux_arm64/dgraph $GOPATH/bin/dgraph
export DGRAPH_BINARY=$GOPATH/bin/dgraph_osx
cd t && ./t --pkg=<package>

After (macOS or Linux)

make install
make test SUITE=systest PKG=systest/export

make help Output

Usage: make [target] [VAR=value ...]

Targets:
  all                  Build all targets
  dgraph               Build dgraph binary
  docker-image         Build Docker image (dgraph/dgraph:$VERSION)
  help                 Show available targets and variables
  image-local          Alias for local-image
  install              Install dgraph binary
  local-image          Build local Docker image (dgraph/dgraph:local)
  test-all             All test suites via t/ runner (i.e. 'make test SUITE=all')
  test-benchmark       Go benchmarks (i.e. 'go test -bench')
  test-core            Core tests (i.e. 'make test SUITE=core')
  test-fuzz            Fuzz tests, auto-discovers packages (i.e. 'make test FUZZ=1')
  test-integration     Integration tests (i.e. 'make test TAGS=integration')
  test-integration2    Integration2 tests via dgraphtest (i.e. 'make test TAGS=integration2')
  test-ldbc            LDBC benchmark tests (i.e. 'make test SUITE=ldbc')
  test-load            Heavy load tests (i.e. 'make test SUITE=load')
  test-systest         System integration tests (i.e. 'make test SUITE=systest')
  test-unit            Unit tests, no Docker (i.e. 'make test SUITE=unit')
  test-upgrade         Upgrade tests (i.e. 'make test TAGS=upgrade')
  test-vector          Vector search tests (i.e. 'make test SUITE=vector')
  test                 Run tests (see 'make help' for options)
  uninstall            Uninstall dgraph binary
  version              Show build version info

Variables that can be passed to 'test':
  SUITE     Select t/ runner suite (e.g., make test SUITE=systest)
  TAGS      Go build tags - bypasses t/ runner (e.g., make test TAGS=integration2)
  PKG       Limit to specific package (e.g., make test PKG=systest/export)
  TEST      Run specific test function (e.g., make test TEST=TestGQLSchema)
  FUZZ      Enable fuzz testing (e.g., make test FUZZ=1)
  FUZZTIME  Fuzz duration per package (e.g., make test FUZZ=1 FUZZTIME=60s)

  Available SUITE values: all  ldbc  load  unit  systest  vector  core
  Available TAGS values:  integration integration2 upgrade

Examples:
  make test TAGS=integration2 PKG=systest/vector        # integration2 tests for vector
  make test TAGS=upgrade PKG=acl TEST=TestACL           # specific upgrade test
  make test FUZZ=1 PKG=dql FUZZTIME=30s                 # fuzz dql package for 30s
  make test SUITE=systest PKG=systest/backup/filesystem # systest for backup pkg
  make test-benchmark PKG=posting                       # benchmark posting package

Test plan

• Run make install on macOS and verify both binaries are created
• Run make check in t/ directory
• Verify make test-unit routes to t/ runner with --suite=unit
• Verify make test TAGS=integration2 PKG=types runs go test directly
• Verify make test FUZZ=1 PKG=dql FUZZTIME=5s runs fuzz tests
• Verify make test-benchmark PKG=types runs benchmarks
• Verify make help shows all targets, variables, and discovered SUITE/TAGS values
• Verify every SUITE value has a corresponding test-* target
• Verify every TAGS value has a corresponding test-* target
• Verify Linux CI still works as expected

[blacksmith-sh]

Found 1 test failure on Blacksmith runners:

Failure

Test	View Logs
github.com/dgraph-io/dgraph/v25/edgraph/TestDropNamespaceErr	View Logs