Adding upstream version 3.0.5.upstream/3.0.5upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 41 insertions, 0 deletions

diff --git a/distro/tests/README.md b/distro/tests/README.md
new file mode 100644
index 0000000..0012dfc
--- /dev/null
+++ b/distro/tests/README.md
@@ -0,0 +1,41 @@
+Requirements
+------------
+
+- ansible
+- vagrant
+- libvirt (+vagrant-libvirt) / virtualbox
+
+Usage
+-----
+
+`vagrant up` command is configured to trigger ansible provisioning
+which configures OBS repository, installs the knot package, creates
+a zone and config file, starts the knot.service and attempts to
+resolve the entry from created zone file.
+
+By default, the *knot-dns-devel* repo is used. To test the
+*knot-dns-latest* or *knot-dns-testing* repo, set it in `repos.yaml`
+(or use the test-distro.sh script which overwrites this file). If
+you're running tests in parallel, they all HAVE TO use the same repo.
+
+Run the following command for every distro (aka directory with
+Vagrantfile):
+
+```
+./test-distro.sh knot-dns-devel debian9
+```
+
+or
+
+```
+./test-distro.sh knot-dns-testing debian9
+```
+
+or
+
+```
+./test-distro.sh knot-dns-latest debian9
+```
+
+At the end of the test, the package version that was tested is
+printed out. Make sure you're testing what you intended to.