1
0
mirror of https://github.com/juanfont/headscale.git synced 2024-12-20 19:09:07 +01:00
juanfont.headscale/integration
Kristoffer Dalby ccedf276ab add a filter case with really large destination set #1372
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
2023-05-03 18:43:57 +02:00
..
dockertestutil Improve generated integration tests 2023-01-30 14:43:03 +01:00
hsic Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
integrationutil Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
tsic trim dockerfiles, script to rebuild test images (#1403) 2023-05-02 10:51:30 +01:00
acl_test.go add a filter case with really large destination set #1372 2023-05-03 18:43:57 +02:00
auth_oidc_test.go Make sure all clients of a user are ready (#1335) 2023-04-12 09:25:51 +02:00
auth_web_flow_test.go Make sure all clients of a user are ready (#1335) 2023-04-12 09:25:51 +02:00
cli_test.go Improve generated integration tests 2023-01-30 14:43:03 +01:00
control.go Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
embedded_derp_test.go Do not use host networking in embedded DERP tests 2023-04-24 12:17:24 +02:00
general_test.go Add node expiry test 2023-02-03 09:26:22 +01:00
README.md Add section about running locally 2023-02-03 16:25:58 +01:00
scenario_test.go
scenario.go trim dockerfiles, script to rebuild test images (#1403) 2023-05-02 10:51:30 +01:00
ssh_test.go
tailscale.go Reuse Ping function for DERP ping 2023-04-24 12:17:24 +02:00
utils.go Reuse Ping function for DERP ping 2023-04-24 12:17:24 +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.