headscale/integration
Kristoffer Dalby 97a909866d Use pingAll helper for all integration pinging
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
2023-02-03 09:26:22 +01:00
..
dockertestutil Improve generated integration tests 2023-01-30 14:43:03 +01:00
hsic Improve generated integration tests 2023-01-30 14:43:03 +01:00
integrationutil Remove some very verbose error outputs 2022-11-21 14:37:50 +01:00
tsic Add logout method to tsic 2022-12-22 00:09:21 +01:00
auth_oidc_test.go Use pingAll helper for all integration pinging 2023-02-03 09:26:22 +01:00
auth_web_flow_test.go Use pingAll helper for all integration pinging 2023-02-03 09:26:22 +01:00
cli_test.go Improve generated integration tests 2023-01-30 14:43:03 +01:00
control.go Improve generated integration tests 2023-01-30 14:43:03 +01:00
general_test.go Use pingAll helper for all integration pinging 2023-02-03 09:26:22 +01:00
README.md Use ripgrep to find list of tests 2023-02-01 10:58:37 +01:00
scenario_test.go Rename [Nn]amespace -> [Uu]ser in go code 2023-01-18 15:40:04 +01:00
scenario.go Improve generated integration tests 2023-01-30 14:43:03 +01:00
ssh_test.go Rename [Nn]amespace -> [Uu]ser in go code 2023-01-18 15:40:04 +01:00
tailscale.go Add logout method to tsic 2022-12-22 00:09:21 +01: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 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.