TheArchive/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2024-11-23 18:15:26 +00:00
Code Issues Packages Projects Releases Wiki Activity
b27e8ab5a1
headscale/integration
History
Juan Font 0030af3fa4
Rename Machine to Node (#1553)
2023-09-24 06:42:05 -05:00
..
dockertestutil give ci more tollerance for timeouts 2023-09-19 10:20:21 -05:00
hsic Rename Machine to Node (#1553) 2023-09-24 06:42:05 -05:00
integrationutil Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
tsic give ci more tollerance for timeouts 2023-09-19 10:20:21 -05:00
acl_test.go General fixups discovered by checking errors 2023-09-05 08:47:43 +02:00
auth_oidc_test.go General fixups discovered by checking errors 2023-09-05 08:47:43 +02:00
auth_web_flow_test.go introduce a version subset we must test against 2023-09-05 08:47:43 +02:00
cli_test.go Rename Machine to Node (#1553) 2023-09-24 06:42:05 -05:00
control.go Rename Machine to Node (#1553) 2023-09-24 06:42:05 -05:00
embedded_derp_test.go add lock around saving ts clients 2023-09-19 10:20:21 -05:00
general_test.go Rename Machine to Node (#1553) 2023-09-24 06:42:05 -05:00
README.md Add section about running locally 2023-02-03 16:25:58 +01:00
run.sh add script to run integration tests 2023-09-05 08:47:43 +02:00
scenario_test.go Handle errors in integration test setups 2023-09-05 08:47:43 +02:00
scenario.go add lock around saving ts clients 2023-09-19 10:20:21 -05:00
ssh_test.go General fixups discovered by checking errors 2023-09-05 08:47:43 +02:00
tailscale.go General fixups discovered by checking errors 2023-09-05 08:47:43 +02:00
utils.go give ci more tollerance for timeouts 2023-09-19 10:20:21 -05: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.