From a6308edd52f3d6b0699fabb6c40a397bc42c76a1 Mon Sep 17 00:00:00 2001 From: Hamish Moffatt <7577172+hmoffatt@users.noreply.github.com> Date: Thu, 12 Dec 2024 15:28:56 +0000 Subject: [PATCH] DOCS: Add instructions for increasing the timeout on integration tests (#3233) Co-authored-by: Tom Limoncelli --- documentation/integration-tests.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/documentation/integration-tests.md b/documentation/integration-tests.md index a0c7baee9..9de029134 100644 --- a/documentation/integration-tests.md +++ b/documentation/integration-tests.md @@ -47,6 +47,14 @@ go test -v -verbose -provider ROUTE53 -end 5 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 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