From c7065e67943e00ac412cc9adb6cc21fe7b1c9a60 Mon Sep 17 00:00:00 2001
From: Tom Limoncelli <tlimoncelli@stackoverflow.com>
Date: Wed, 22 Nov 2023 09:30:24 -0500
Subject: [PATCH] DOCS: Expand integration tests explanation (#2645)

---
 documentation/integration-tests.md | 21 ++++++++++++++++++---
 1 file changed, 18 insertions(+), 3 deletions(-)

diff --git a/documentation/integration-tests.md b/documentation/integration-tests.md
index dd068edaa..f47327205 100644
--- a/documentation/integration-tests.md
+++ b/documentation/integration-tests.md
@@ -12,8 +12,9 @@ For each step, it will run the config once and expect changes. It will run it ag
 
 ## Running a test
 
-1. Define all environment variables expected for the provider you wish to run. I setup a local `.env` file with the appropriate values and use [zoo](https://github.com/jsonmaur/zoo) to run my commands.
-2. run `go test -v -provider $NAME` where $NAME is the name of the provider you wish to run.
+1. The integration tests need a test domain to run on. All the records of this domain will be deleted!
+2. Define all environment variables expected for the provider you wish to run. I setup a local `.env` file with the appropriate values and use [zoo](https://github.com/jsonmaur/zoo) to run my commands.
+3. run `go test -v -provider $NAME` where $NAME is the name of the provider you wish to run.
 
 Example:
 
@@ -37,8 +38,22 @@ export ROUTE53_DOMAIN="testdomain.tld"
 go test -v -verbose -provider ROUTE53
 ```
 
+The `-start` and `-end` flags allow you to run just a portion of the tests.
+
+```shell
+go test -v -verbose -provider ROUTE53 -start 16
+go test -v -verbose -provider ROUTE53 -end 5
+go test -v -verbose -provider ROUTE53 -start 16 -end 20
+```
+
+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
+`func makeTests` for instructions.
+
+
 {% hint style="warning" %}
-**WARNING**: The records in the test domain will be deleted.  Only use
+**WARNING**: THE RECORDS IN THE TEST DOMAIN WILL BE DELETED.  Only use
 a domain that is not used in production. Some providers have a way
 to run tests on domains that aren't registered (often a test
 environment or a side-effect of the company not being a registrar).