[Reproducible-commits] [reprotest] 01/02: Add instructions for running the tests

[Ceridwen]

This is an automated email from the git hooks/post-receive script.

ceridwen-guest pushed a commit to branch virtualization
in repository reprotest.

commit 28a7008ee33e36cb75e10c70a1c307e50e67b7e0
Author: Ceridwen <ceridwenv at gmail.com>
Date:   Tue Jul 19 17:04:33 2016 -0400

    Add instructions for running the tests
---
 README.md | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)

diff --git a/README.md b/README.md
index 1efa9f3..9f72c22 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,6 @@
+Command Line Interface
+=====================
+
 reprotest's CLI takes two mandatory arguments, the build command to
 run and the build artifact file to test after running the build.  If
 the build command or build artifact have spaces, they have to be
@@ -14,6 +17,11 @@ build command in and defaults to the current working directory; and
 --verbose, which will eventually enable more detailed logging.  To get
 help for the CLI, run `reprotest -h` or `reprotest --help`.
 
+
+
+Config File
+===========
+
 The config file has one section, basics, and the same options as the
 CLI, except there's no dont_vary option, and there are `build_command`
 and `artifact` options.  If `build_command` and/or `artifact` are set
@@ -41,3 +49,50 @@ directory.  A sample config file is below.
       timezone
       umask
       user_group
+
+
+
+Running the Tests
+=================
+
+The easiest way to run the tests is with
+[Tox](https://pypi.python.org/pypi/tox).  Install it,
+[Coverage](https://pypi.python.org/pypi/coverage), and
+[pytest](https://pypi.python.org/pypi/pytest).  (On Debian, this can
+be done with `apt-get install python3-coverage tox python3-pytest`.)
+Next, setup the virtualization servers, for null (no virtualization),
+schroot, and qemu.
+
+Some of the following instructions rely on Debian utilities.  For
+schroot, run `mk-sbuild --debootstrap-include=devscripts stable`.  (If
+you aren't on `amd64`, you'll have to include `--arch`.)  For qemu,
+first `apt-get install autopkgtest vmdebootstrap qemu`, then run:
+
+    vmdebootstrap --verbose --serial-console --distribution=sid \
+                 --customize=/usr/share/autopkgtest/setup-commands/setup-testbed \
+                 --user=adt/adt --size=10000000000 --grub --image=adt-sid.raw
+    qemu-img convert -O qcow2 adt-sid.raw  adt-sid.img
+    rm adt-sid.raw
+
+The last two commands reduce the size of the image but aren't strictly
+necessary.  Move `adt-sid.img` to `linux/` under your home directory.
+
+To log into the schroot and qemu containers, respectively, run:
+
+    sudo schroot -c source:stable-amd64
+    qemu-system-x86_64 -enable-kvm -drive file=~/linux/adt-sid.img,if=virtio -net user -net nic,model=virtio -m 1024
+
+After replacing `~` with your home directory.
+
+For the host system and the two containers, run:
+
+    apt-get install disorderfs
+    (Additionally for mk-sbuild stable,  enable the backports repository.)
+    (Additionally for chroot, run:
+    mknod -m 666 /dev/fuse c 10 229)
+    apt-get install python3 python3-pip
+    apt-get install locales-all
+
+Then, clone the repository.  Go to the root of the repository, where
+`tox.ini` is, and run `tox`.  For more verbose output, run `tox --
+-s`.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reprotest.git