StackExchange/dnscontrol
1
1
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2024-12-26 09:42:18 +08:00
Code Issues Projects Releases Packages Wiki Activity

DOCS: Add instructions for increasing the timeout on integration tests (#3233)

Browse source 
Co-authored-by: Tom Limoncelli <tlimoncelli@stackoverflow.com>
This commit is contained in:
Hamish Moffatt 2024-12-12 15:28:56 +00:00 committed by GitHub
parent de6afe2506
commit a6308edd52
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
documentation/integration-tests.md
View file

@ -47,6 +47,14 @@ go test -v -verbose -provider ROUTE53 -end 5
go test -v -verbose -provider ROUTE53 -start 16 -end 20 go test -v -verbose -provider ROUTE53 -start 16 -end 20
``` ```
For some providers it may be necessary to increase the test timeout using `-test`. The default is 10 minutes. `0` is "no limit". Typical Go durations work too (`1h` for 1 hour, etc).
```shell
go test -timeout 0 -v -verbose -provider CLOUDNS
```
FYI: The order of the flags matters. Flags native to the Go testing suite (`-timeout` and `-v`) must come before flags that are part of the DNSControl integration tests (`-verbose`, `-provider`). Yeah, that sucks and is confusing.
The actual tests are in the file `integrationTest/integration_test.go`. The The actual tests are in the file `integrationTest/integration_test.go`. The
tests are in a little language which can be used to describe just about any tests are in a little language which can be used to describe just about any
interaction with the API. Look for the comment `START HERE` or the line interaction with the API. Look for the comment `START HERE` or the line