headscale/integration
Kristoffer Dalby e9a94f00a9 integration: update SSH tests for validation rules
Update integration tests to use valid SSH patterns:

- TestSSHOneUserToAll: use autogroup:member and autogroup:tagged
  instead of wildcard destination
- TestSSHMultipleUsersAllToAll: use autogroup:self instead of
  username destinations for group-to-user SSH access

Updates #3009
Updates #3010
2026-01-21 17:01:30 +00:00
..
dockertestutil
dsic integration: add run ID isolation for concurrent test execution 2026-01-09 12:34:16 +01:00
hsic integration: add tests for ACL group with deleted/unknown users 2026-01-20 15:41:19 +01:00
integrationutil
tsic integration: add run ID isolation for concurrent test execution 2026-01-09 12:34:16 +01:00
acl_test.go state: add unit test for DeleteUser change signal 2026-01-20 15:41:19 +01:00
api_auth_test.go
auth_key_test.go integration: update CLI tests for ID-based preauthkey commands 2026-01-20 12:53:20 +01:00
auth_oidc_test.go
auth_web_flow_test.go
cli_test.go integration: add tests for API key expire/delete by ID 2026-01-20 17:13:38 +01:00
control.go integration: add tests for ACL group with deleted/unknown users 2026-01-20 15:41:19 +01:00
derp_verify_endpoint_test.go
dns_test.go
embedded_derp_test.go
general_test.go
helpers.go
README.md
route_test.go integration: prepare AutoApprove test for new tags 2025-12-17 09:32:05 +01:00
run.sh
scenario.go integration: support auth keys without user 2026-01-20 12:53:20 +01:00
scenario_test.go
ssh_test.go integration: update SSH tests for validation rules 2026-01-21 17:01:30 +00:00
tags_test.go integration: fix tags-only auth key tests 2026-01-20 12:53:20 +01:00
tailscale.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, a local GitHub Actions runner:

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