headscale/integration
Juan Font 580f96ce83 Remove unused node check interval 2024-04-17 20:20:44 +02:00
..
dockertestutil give ci more tollerance for timeouts 2023-09-19 10:20:21 -05:00
hsic Remove unused node check interval 2024-04-17 20:20:44 +02:00
integrationutil Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
tsic Rework map session 2024-04-15 12:31:53 +02:00
README.md Add section about running locally 2023-02-03 16:25:58 +01:00
acl_test.go new IP allocator and add postgres to integration tests. (#1756) 2024-02-18 19:31:29 +01:00
auth_oidc_test.go Rework map session 2024-04-15 12:31:53 +02:00
auth_web_flow_test.go Rework map session 2024-04-15 12:31:53 +02:00
cli_test.go new IP allocator and add postgres to integration tests. (#1756) 2024-02-18 19:31:29 +01:00
control.go Rename Machine to Node (#1553) 2023-09-24 06:42:05 -05:00
embedded_derp_test.go move "embedded derp" settings into With options for integration tests (#1872) 2024-04-16 21:37:25 +02:00
general_test.go Migrate IP fields in database to dedicated columns (#1869) 2024-04-17 07:03:06 +02:00
route_test.go improve testing of route failover logic 2024-04-15 12:31:53 +02:00
run.sh implement selfupdate and pass expiry (#1647) 2024-01-05 10:41:56 +01:00
scenario.go Rework map session 2024-04-15 12:31:53 +02:00
scenario_test.go implement selfupdate and pass expiry (#1647) 2024-01-05 10:41:56 +01:00
ssh_test.go ensure online status and route changes are propagated (#1564) 2023-12-09 18:09:24 +01:00
tailscale.go Rework map session 2024-04-15 12:31:53 +02:00
utils.go Rework map session 2024-04-15 12:31:53 +02:00

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](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.