mirror of
https://github.com/juanfont/headscale.git
synced 2026-04-07 21:47:46 +09:00
a739862c65
Add integration tests validating that via grants correctly steer routes to designated nodes per client group: - TestGrantViaSubnetSteering: two routers advertise the same subnet, via grants steer each client group to a specific router. Verifies per-client route visibility, curl reachability, and traceroute path. - TestGrantViaExitNodeSteering: two exit nodes, via grants steer each client group to a designated exit node. Verifies exit routes are withdrawn from non-designated nodes and the client rejects setting a non-designated exit node. - TestGrantViaMixedSteering: cross-steering where subnet routes and exit routes go to different servers per client group. Verifies subnet traffic uses the subnet-designated server while exit traffic uses the exit-designated server. Also add autogroupp helper for constructing AutoGroup aliases in grant policy configurations. Updates #2180
Integration testing
Headscale relies on integration testing to ensure we remain compatible with Tailscale.
This is typically performed by starting a Headscale server and running a test "scenario" with an array of Tailscale clients and versions.
Headscale's test framework and the current set of scenarios are defined in this directory.
Tests are located in files ending with _test.go and the framework are located in the rest.
Running integration tests locally
The easiest way to run tests locally is to use act, a local GitHub Actions runner:
act pull_request -W .github/workflows/test-integration.yaml
Alternatively, the docker run command in each GitHub workflow file can be used.
Running integration tests on GitHub Actions
Each test currently runs as a separate workflows in GitHub actions, to add new test, run
go generate inside ../cmd/gh-action-integration-generator/ and commit the result.