From 3a4bbc1f799d0a19f9e56a4a931eb8431f6a6515 Mon Sep 17 00:00:00 2001 From: iexos Date: Sat, 21 Feb 2026 19:37:50 +0100 Subject: [PATCH] add & fix some abra testing notes --- docs/abra/hack.md | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/docs/abra/hack.md b/docs/abra/hack.md index a9507ab..ed09500 100644 --- a/docs/abra/hack.md +++ b/docs/abra/hack.md @@ -182,31 +182,45 @@ For some tests an actual server is needed, where apps can be deployed. You can e ##### Remote swarm +!!! warning + + Right now, the test suite will check for a local swarm, see [abra/#769](https://git.coopcloud.tech/toolshed/abra/issues/769) + ``` export TEST_SERVER="test.example.com" export ABRA_DIR="$HOME/.abra_test" ``` -`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. The test suite does not deploy Traefik for you. +There should also be a DNS A record for `*.test.example.com` which points to the same server so that the test suite can deploy apps freely. The test suite does not deploy Traefik for you. ##### Local swarm -When running the test suite localy you need a running docker swarm setup: +!!! note + + This is currently necessary even if you only want to run tests which don't need a server + +When running the test suite locally you need a running docker swarm setup: ``` docker swarm init docker network create -d overlay proxy ``` -To use the local swarm set the foloowing env var: +To use the local swarm set the following env var: ``` export TEST_SERVER=default export ABRA_DIR="$HOME/.abra_test" ``` +Make sure that the user running the tests can access the docker socket e.g. by adding it to the `docker` group (security considerations apply). + ### Run tests +!!! note + + You need to remember to compile your current version of `abra` via `make` before running the tests. See [abra/#770](https://git.coopcloud.tech/toolshed/abra/issues/770) + Now you can run the whole test suite: ```