mirror of
https://github.com/juanfont/headscale.git
synced 2024-11-25 02:55:29 +00:00
35bfe7ced0
* Add support for service reload and sync service file * Copy the systemd.service file to the manual linux docs and adjust the path to the headscale binary to match with the previous documentation blocks. Unfortunately, there seems to be no easy way to include a file in mkdocs. * Remove a redundant "deprecation" block. The beginning of the documentation already states that. * Add `ExecReload` to the systemd.service file. Fixes: #2016 * Its called systemd * Fix link to systemd homepage |
||
---|---|---|
.. | ||
dockertestutil | ||
hsic | ||
integrationutil | ||
tsic | ||
acl_test.go | ||
auth_oidc_test.go | ||
auth_web_flow_test.go | ||
cli_test.go | ||
control.go | ||
dns_test.go | ||
embedded_derp_test.go | ||
general_test.go | ||
README.md | ||
route_test.go | ||
run.sh | ||
scenario_test.go | ||
scenario.go | ||
ssh_test.go | ||
tailscale.go | ||
utils.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](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.