headscale/integration
Kristoffer Dalby 64319f79ff
make stream shutdown if self-node has been removed (#2125)
* add shutdown that asserts if headscale had panics

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* add test case producing 2118 panic

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

* make stream shutdown if self-node has been removed

Currently we will read the node from database, and since it is
deleted, the id might be set to nil. Keep the node around and
just shutdown, so it is cleanly removed from notifier.

Fixes #2118

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>

---------

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
2024-09-11 12:00:32 +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 Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
tsic make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
acl_test.go feat: implements apis for managing headscale policy (#1792) 2024-07-18 07:38:25 +02:00
auth_oidc_test.go metrics, tuning in tests, db cleanups, fix concurrency issue (#1895) 2024-04-21 18:28:17 +02:00
auth_web_flow_test.go metrics, tuning in tests, db cleanups, fix concurrency issue (#1895) 2024-04-21 18:28:17 +02:00
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 test embedded derp with derp updater, check client health (#2030) 2024-08-11 07:44:59 +02:00
general_test.go make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
README.md Add section about running locally 2023-02-03 16:25:58 +01:00
route_test.go 2068 AutoApprovers tests (#2105) 2024-09-05 16:46:20 +02:00
run.sh Fix 764 (#2093) 2024-09-03 09:22:17 +02:00
scenario_test.go metrics, tuning in tests, db cleanups, fix concurrency issue (#1895) 2024-04-21 18:28:17 +02:00
scenario.go make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
ssh_test.go metrics, tuning in tests, db cleanups, fix concurrency issue (#1895) 2024-04-21 18:28:17 +02:00
tailscale.go Redo DNS configuration (#2034) 2024-08-19 11:41:05 +02:00
utils.go Fix typos (#1860) 2024-05-19 23:49:27 +02:00

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.