mirror of https://github.com/juanfont/headscale.git synced 2025-12-24 15:06:42 +00:00

Files

Kristoffer Dalby f67ed36fe2 integration: replicate tag propagation issue

This commit adds tests to validate that there are
issues with how we propagate tag changes in the system.

This replicates #2389

Signed-off-by: Kristoffer Dalby <kristoffer@dalby.cc>

2025-12-16 10:12:36 +01:00

dockertestutil

…

dsic

…

hsic

…

integrationutil

…

tsic

…

acl_test.go

…

api_auth_test.go

…

auth_key_test.go

…

auth_oidc_test.go

…

auth_web_flow_test.go

…

cli_test.go

…

control.go

…

derp_verify_endpoint_test.go

…

dns_test.go

…

embedded_derp_test.go

…

general_test.go

…

helpers.go

…

README.md

…

route_test.go

…

run.sh

…

scenario_test.go

…

scenario.go

…

ssh_test.go

…

tags_test.go

…

tailscale.go

…

README.md

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.