mirror of
https://github.com/juanfont/headscale.git
synced 2024-11-26 08:53:05 +00:00
83769ba715
This commits removes the locks used to guard data integrity for the database and replaces them with Transactions, turns out that SQL had a way to deal with this all along. This reduces the complexity we had with multiple locks that might stack or recurse (database, nofitifer, mapper). All notifications and state updates are now triggered _after_ a database change. Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com> |
||
|---|---|---|
| .. | ||
| dockertestutil | ||
| hsic | ||
| integrationutil | ||
| tsic | ||
| acl_test.go | ||
| auth_oidc_test.go | ||
| auth_web_flow_test.go | ||
| cli_test.go | ||
| control.go | ||
| embedded_derp_test.go | ||
| general_test.go | ||
| README.md | ||
| route_test.go | ||
| run.sh | ||
| scenario.go | ||
| scenario_test.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.