1
0
mirror of https://github.com/juanfont/headscale.git synced 2025-10-05 11:19:03 +02:00
juanfont.headscale/integration
Kristoffer Dalby 1ec99c55e4
add test to reproduce #2129
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
2024-09-13 07:22:24 +02:00
..
dockertestutil make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
hsic make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
integrationutil
tsic make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
acl_test.go
auth_oidc_test.go
auth_web_flow_test.go
cli_test.go Only load needed part of configuration (#2109) 2024-09-07 09:23:58 +02:00
control.go make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
dns_test.go Add support for service reload and sync service file (#2102) 2024-09-05 10:08:50 +00:00
embedded_derp_test.go
general_test.go make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
README.md
route_test.go add test to reproduce #2129 2024-09-13 07:22:24 +02:00
run.sh Fix 764 (#2093) 2024-09-03 09:22:17 +02:00
scenario_test.go Update documentation for Apple (#2117) 2024-09-11 18:43:59 +02:00
scenario.go add test to reproduce #2129 2024-09-13 07:22:24 +02:00
ssh_test.go
tailscale.go
utils.go

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](INSERT LINK), a local GitHub Actions runner:

act pull_request -W .github/workflows/test-integration-v2-TestPingAllByIP.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.