Mirrors/juanfont.headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2024-10-17 20:05:55 +02:00
Code Issues Projects Releases Wiki Activity
f039caf134
juanfont.headscale/integration
History
Mike Poindexter 3101f895a7
Fix 764 (#2093) 
* Fix KeyExpiration when a zero time value has a timezone

When a zero time value is loaded from JSON or a DB in a way that
assigns it the local timezone, it does not roudtrip in JSON as a
value for which IsZero returns true. This causes KeyExpiry to be
treated as a far past value instead of a nilish value.

See https://github.com/golang/go/issues/57040

* Fix whitespace

* Ensure that postgresql is used for all tests when env var is set

* Pass through value of HEADSCALE_INTEGRATION_POSTGRES env var

* Add option to set timezone on headscale container

* Add test for registration with auth key in alternate timezone
2024-09-03 09:22:17 +02:00
..
dockertestutil validate policy against nodes, error if not valid (#2089) 2024-08-30 16:58:29 +02:00
hsic Fix 764 (#2093) 2024-09-03 09:22:17 +02:00
integrationutil
tsic Redo DNS configuration (#2034) 2024-08-19 11:41:05 +02:00
acl_test.go
auth_oidc_test.go
auth_web_flow_test.go
cli_test.go validate policy against nodes, error if not valid (#2089) 2024-08-30 16:58:29 +02:00
control.go
dns_test.go Redo DNS configuration (#2034) 2024-08-19 11:41:05 +02:00
embedded_derp_test.go
general_test.go Fix 764 (#2093) 2024-09-03 09:22:17 +02:00
README.md
route_test.go fix route table migration wiping routes 0.22 -> 0.23 (#2076) 2024-08-27 18:54:28 +02:00
run.sh Fix 764 (#2093) 2024-09-03 09:22:17 +02:00
scenario_test.go
scenario.go Fix 764 (#2093) 2024-09-03 09:22:17 +02:00
ssh_test.go
tailscale.go Redo DNS configuration (#2034) 2024-08-19 11:41:05 +02:00
utils.go

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.