You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Kristoffer Dalby
1c6bfc503c
|
2 weeks ago | |
---|---|---|
.. | ||
dockertestutil | 8 months ago | |
hsic | 3 weeks ago | |
integrationutil | 1 year ago | |
tsic | 1 month ago | |
README.md | 1 year ago | |
acl_test.go | 4 weeks ago | |
auth_oidc_test.go | 4 weeks ago | |
auth_web_flow_test.go | 4 weeks ago | |
cli_test.go | 2 weeks ago | |
control.go | 8 months ago | |
embedded_derp_test.go | 4 weeks ago | |
general_test.go | 4 weeks ago | |
route_test.go | 3 weeks ago | |
run.sh | 5 months ago | |
scenario.go | 4 weeks ago | |
scenario_test.go | 4 weeks ago | |
ssh_test.go | 4 weeks ago | |
tailscale.go | 1 month ago | |
utils.go | 1 month ago |
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.