https://github.com/linbit/vmshed
shedules tests with virter
https://github.com/linbit/vmshed
Last synced: about 1 year ago
JSON representation
shedules tests with virter
- Host: GitHub
- URL: https://github.com/linbit/vmshed
- Owner: LINBIT
- License: gpl-2.0
- Created: 2020-07-07T13:29:51.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2025-03-18T07:15:12.000Z (over 1 year ago)
- Last Synced: 2025-04-02T19:11:33.593Z (about 1 year ago)
- Language: Go
- Size: 282 KB
- Stars: 8
- Watchers: 8
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# vmshed
vmshed is a shed for storing your VMs. More precisely, it is a s(c)heduler for
running tests in VMs.
## Usage
vmshed basically takes as input two configuration files, one that defines the
tests ("tests specification"), and one that defines the set of VMs ("VMs
specification"). Then it executes tests concurrently and collects the result
and if desired prepares output in the JUnit format.
Example:
```
vmshed --tests example/tests.example.toml --vms example/vms.example.toml
```
The test runs are determined based on these specification files and the command
line flags as described [here](doc/test-run-determination.md).
## Tests specification
The tests specification is a TOML file that is provided with the `--tests`
flag. It defines what tests there are and how they are run.
[Tests specification](./doc/tests-specification.md) describes the available
keys.
### Test suite file
The top level key `test_suite_file` in the tests specification references
a virter provisioning file which is run with `virter vm exec`. This executes
one test.
The environment variable `TEST_NAME` contains the name of the test to be run.
To override values in the provisioning file, use the `--set` flag.