Commit graph

4 commits

Author SHA1 Message Date
Frederik Ring
7ab06cea59
Current test setup is too restrictive, allow running a series of executables in different contexts instead (#597)
* Current test setup is too restrictive, allow running a series of executables in different contexts instead

* Split existing tests that test against swarm
2025-06-11 19:46:41 +02:00
Frederik Ring
0ce19a4ff2
Fall back to default behavior when deployed to a worker node (#593)
* Add test demonstrating failure when running on worker node

* Consider manager status when checking for swarm related features

* Update documentation
2025-06-09 14:19:18 +02:00
Frederik Ring
06bb25c980
Defining test sandbox in compose file allows testing against multi node swarm setup (#591)
* Defining test sandbox in compose file allows swapping with multi node swarm setup

* Test cases can request a multi node swarm cluster

* Docker healthchecks can be used for awaiting ready state

* Compose profiles can be used
2025-06-06 17:46:25 +02:00
Frederik Ring
1e39ac41f4
Run tests Docker in Docker (#261)
* Try running tests in Docker

* Spawn new container for each test

* Store test artifacts outside of mount

* When requested, build up to date image in test script

* sudo is unneccessary in containerized test env

* Skip azure test

* Backdate fixture file in JSON database

* Pin versions for azure tools

* Mount temp volume for /var/lib/docker to prevent dangling ones created by VOLUME instruction

* Fail backdating tests with message

* Add some documentation on test setup

* Cache images

* Run compose stacks with shortened default timeout
2023-09-02 15:17:46 +02:00