myriation/headscale
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity
headscale/integration
History
Kristoffer Dalby 14e29a7bee create DB struct 
This is step one in detaching the Database layer from Headscale (h). The
ultimate goal is to have all function that does database operations in
its own package, and keep the business logic and writing separate.

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
2023-05-26 12:24:50 +02:00
..
dockertestutil Improve generated integration tests 2023-01-30 14:43:03 +01:00
hsic create DB struct 2023-05-26 12:24:50 +02:00
integrationutil Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
tsic create DB struct 2023-05-26 12:24:50 +02:00
acl_test.go update dependency path for integration 2023-05-10 20:47:51 +02:00
auth_oidc_test.go create DB struct 2023-05-26 12:24:50 +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 port reminder of integrationv1 test to v2 2023-05-10 20:47:51 +02: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 create DB struct 2023-05-26 12:24:50 +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.go create DB struct 2023-05-26 12:24:50 +02:00
scenario_test.go Rename [Nn]amespace -> [Uu]ser in go code 2023-01-18 15:40:04 +01:00
ssh_test.go update dependency path for integration 2023-05-10 20:47:51 +02:00
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

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.