mirror of
https://github.com/juanfont/headscale.git
synced 2026-01-23 02:24:10 +00:00
c4600346f9
Some checks failed
Build / build-nix (push) Has been cancelled
Build / build-cross (GOARCH=amd64 GOOS=darwin) (push) Has been cancelled
Build / build-cross (GOARCH=amd64 GOOS=linux) (push) Has been cancelled
Build / build-cross (GOARCH=arm64 GOOS=darwin) (push) Has been cancelled
Build / build-cross (GOARCH=arm64 GOOS=linux) (push) Has been cancelled
Check Generated Files / check-generated (push) Has been cancelled
NixOS Module Tests / nix-module-check (push) Has been cancelled
Tests / test (push) Has been cancelled
This PR restructures the integration tests and prebuilds all common assets used in all tests: Headscale and Tailscale HEAD image hi binary that is used to run tests go cache is warmed up for compilation of the test This essentially means we spend 6-10 minutes building assets before any tests starts, when that is done, all tests can just sprint through. It looks like we are saving 3-9 minutes per test, and since we are limited to running max 20 concurrent tests across the repo, that means we had a lot of double work. There is currently 113 checks, so we have to do five runs of 20, and the saving should be quite noticeable! I think the "worst case" saving would be 20+min and "best case" probably towards an hour. |
||
|---|---|---|
| .. | ||
| dockertestutil | ||
| dsic | ||
| hsic | ||
| integrationutil | ||
| tsic | ||
| acl_test.go | ||
| api_auth_test.go | ||
| auth_key_test.go | ||
| auth_oidc_test.go | ||
| auth_web_flow_test.go | ||
| cli_test.go | ||
| control.go | ||
| derp_verify_endpoint_test.go | ||
| dns_test.go | ||
| embedded_derp_test.go | ||
| general_test.go | ||
| helpers.go | ||
| README.md | ||
| route_test.go | ||
| run.sh | ||
| scenario.go | ||
| scenario_test.go | ||
| ssh_test.go | ||
| tags_test.go | ||
| 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.