simon/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Pull Requests Activity

docs: more getting started help

Browse Source
This commit is contained in:
decentral1se 2023-09-20 14:44:33 +02:00
parent 87b7d403fb
commit 7f0c8abceb
Signed by untrusted user: decentral1se
GPG Key ID: 03789458B3D0C410
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/abra/hack.md
View File

@ -50,7 +50,7 @@ Then you can run the integration test suite with the following.
``` ```
export ABRA_TEST_DOMAIN="test.example.com" export ABRA_TEST_DOMAIN="test.example.com"
export ABRA_DIR="$HOME/.abra_test" export ABRA_DIR="$HOME/.abra_test"
bats -Tp tests/integration bats -Tp tests/integration # DO NOT run this just yet, read below...
``` ```
`ABRA_TEST_DOMAIN` should also have a DNS A record for `*.test.example.com` `ABRA_TEST_DOMAIN` should also have a DNS A record for `*.test.example.com`
@ -59,6 +59,13 @@ It's advised that you re-use the same server and therefore the same Traefik
deployment for running your integration tests. The test suite does not deploy deployment for running your integration tests. The test suite does not deploy
Traefik for you. Then you'll have more stable results. Traefik for you. Then you'll have more stable results.
You probably don't want to run the entire test suite though, it takes a while.
Try the following for starters.
```
bats -Tp tests/integration/autocomplete.bats
```
### Tagging tests ### Tagging tests
When a test actually deploys something to a server, we tag it with the following: When a test actually deploys something to a server, we tag it with the following:
@ -78,6 +85,12 @@ for more.
### Filter tests ### Filter tests
You can run a specific file.
```
bats -Tp tests/integration/autocomplete.bats
```
You can filter on test names to run specific kinds of tests. You can filter on test names to run specific kinds of tests.
``` ```