coop-cloud/docs.coopcloud.tech
coop-cloud
/
docs.coopcloud.tech
4
1
Fork 14
Code Issues Pull Requests 2 Releases Activity

docs: moar moar integration suite docs
continuous-integration/drone/push Build is passing Details

This commit is contained in:
decentral1se 2023-09-07 17:09:41 +02:00
parent 9eb32ce6f2
commit d324d050cd
Signed by: decentral1se
GPG Key ID: 03789458B3D0C410
1 changed files with 21 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/abra/hack.md
View File

@ -33,13 +33,31 @@ apt install bats bats-file bats-assert bats-support jq make git
Then you can run the integration test suite with the following:
```
export TEST_DOMAIN="test.example.com"
export ABRA_TEST_DOMAIN="test.example.com"
export ABRA_DIR="$HOME/.abra_test"
bats tests/integration
```
`TEST_DOMAIN` should also have a DNS A record for `*.test.example.com` which
points to the same server so that the test suite can deploy apps freely.
`ABRA_TEST_DOMAIN` should also have a DNS A record for `*.test.example.com`
which points to the same server so that the test suite can deploy apps freely.
If you're hacking on the tests, you can speed things up with the following.
```
export ABRA_SKIP_TEARDOWN=1
```
This will avoid nuking `$ABRA_DIR` for each test which avoids the costly `git
clone` of the catalogue on each test run. For the actual CI testing, we
probably want this clean slate on each test to avoid confusion.
You can filter on test names and/or tags to run specific kinds of tests.
```
bats tests/integration \
--filter "validate app argument" \
--filter-tags "app_backup,\!slow"
```
## Using the `abra` public API