History

Tom Gundersen ba846aafcf test: test the in-tree version of our tool Make sure we test the version of osbuild in the current checkout, rather than the system instance. Also default to using in-place directories for the object store and output images. Using a tmpfs does not scale, especially on CI infrastructue with limited memory. The behavior can still be overridden by the environment variable, as before, only the default changes. Signed-off-by: Tom Gundersen <teg@jklm.no>		2019-08-30 12:00:47 +02:00
..
integration_tests	test: test the in-tree version of our tool	2019-08-30 12:00:47 +02:00
pipelines	test: make the testsuite passive rather than active	2019-08-30 12:00:47 +02:00
testing-rpms	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
.gitignore	introduce testing script	2019-07-09 10:29:48 +02:00
__init__.py	osbuild: add description() methods	2019-08-07 10:01:17 +02:00
__main__.py	test: make the testsuite passive rather than active	2019-08-30 12:00:47 +02:00
Makefile	make vagrant-test idempotent	2019-07-25 15:47:53 +02:00
README.md	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
test_osbuild.py	Pipeline: drop the build setter	2019-08-13 17:13:13 +02:00
Vagrantfile	make vagrant-test idempotent	2019-07-25 15:47:53 +02:00

README.md

Setup

To run the tests in vagrant virtual machine, please follow this tutorial: https://developer.fedoraproject.org/tools/vagrant/vagrant-libvirt.html

(run also sudo systemctl start libvirtd)

Using Vagrant

To start a Vagrant box by hand, run vagrant up in this directory. To stop and remove all volumes run vagrant destroy again in this directory.

Troubleshooting

In case you accidentally deleted .vagrant directory, you can use some of these commands in order to get rid of running instance:

$ virsh list # this should display test_default
$ virsh managedsave-remove test_default
$ virsh undefine test_default
# or using vagrant cli tool
$ vagrant global-status
$ vagrant destroy <id>
$ vagrant global-status --prune