headscale/integration
Kristoffer Dalby ceeef40cdf
Add tests to verify "Hosts" aliases in ACL (#1304)
2023-04-03 10:08:48 +02:00
..
dockertestutil Improve generated integration tests 2023-01-30 14:43:03 +01:00
hsic Fix various linting issues + golang-lint upgrade (#1245) 2023-03-03 18:22:47 +01:00
integrationutil Remove some very verbose error outputs 2022-11-21 14:37:50 +01:00
tsic Add ACL test for limiting a single port. (#1258) 2023-03-20 08:52:52 +01:00
README.md Add section about running locally 2023-02-03 16:25:58 +01:00
acl_test.go Add tests to verify "Hosts" aliases in ACL (#1304) 2023-04-03 10:08:48 +02: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 Add node expiry test 2023-02-03 09:26:22 +01:00
scenario.go Add documentation to integration test framework 2023-02-03 16:25:58 +01:00
scenario_test.go Rename [Nn]amespace -> [Uu]ser in go code 2023-01-18 15:40:04 +01:00
ssh_test.go Rename [Nn]amespace -> [Uu]ser in go code 2023-01-18 15:40:04 +01:00
tailscale.go Add ACL test for limiting a single port. (#1258) 2023-03-20 08:52:52 +01:00
utils.go Add node expiry test 2023-02-03 09:26:22 +01: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.