mirror of
https://github.com/juanfont/headscale.git
synced 2026-04-01 15:03:23 +02:00
f1e5f1346d
TestACLTagPropagationPortSpecific failed twice on CI because it jumped from SetNodeTags directly to checking curl, without first verifying the tag change was applied on the server. This races against server-side processing. Add a tag verification step (matching TestACLTagPropagation's pattern) and bump the Step 4 timeout from 60s to 90s since port-specific filter changes require both endpoints to process the new PacketFilter from the MapResponse while the WireGuard tunnel stays up. Updates #3125
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.