History

Lars Karlitski 2ab9ba4e33 test: refactor boot test Use the unittest module from the standard library. Also, ensure that separate runs of this test don't share a osbuild store and clean up after themselves. With contributions from Ondřej Budai and Tom Gundersen.		2019-09-26 19:20:47 +02:00
..
integration_tests	osbuild: store outputs in objectstore	2019-09-25 23:50:50 +02:00
pipelines	stages/dnf: verify repository checksum	2019-09-24 20:17:04 +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: refactor boot test	2019-09-26 19:20:47 +02:00
Makefile	make vagrant-test idempotent	2019-07-25 15:47:53 +02:00
osbuildtest.py	test: refactor boot test	2019-09-26 19:20:47 +02:00
README.md	improve vagrant test and its documentation	2019-07-25 12:46:53 +02:00
test_boot.py	test: refactor boot test	2019-09-26 19:20:47 +02:00
test_osbuild.py	pipeline: introduce output id	2019-09-25 23:50:50 +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