From 26cc25d066005ff8161fbdf8565ecbb328e93d88 Mon Sep 17 00:00:00 2001
From: Wojciech Zygmunt Porczyk <woju@invisiblethingslab.com>
Date: Tue, 13 Jan 2015 23:34:22 +0000
Subject: [PATCH] TestBench changed

created
---
 TestBench.md | 143 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 143 insertions(+)
 create mode 100644 TestBench.md

diff --git a/TestBench.md b/TestBench.md
new file mode 100644
index 00000000..1363fe01
--- /dev/null
+++ b/TestBench.md
@@ -0,0 +1,143 @@
+---
+layout: wiki
+title: TestBench
+permalink: /wiki/TestBench/
+---
+
+Test bench for Dom0
+===================
+
+This guide shows how to set up simple test bench that automatically test your code you're about to push. It is written especially for `core3` branch of `core-admin.git` repo, but some ideas are universal.
+
+We will set up a spare machine (bare metal, not a virtual) that will be hosting our experimental Dom0. We will communicate with it via Ethernet and SSH. This tutorial assumes you are familiar with [QubesBuilder](/wiki/QubesBuilder) and you have it set up and running flawlessly.
+
+Setting up the machine
+----------------------
+
+First, do a clean install from ISO you built or grabbed elsewhere.
+
+You have to fix network, because it is intentionally broken. This script should reenable your network card without depending on anything else.
+
+    #!/bin/sh
+
+    # adjust this for your NIC (run lspci)
+    BDF=0000:02:00.0
+
+    prog=$(basename $0)
+
+    pciunbind() {
+        local path
+        path=/sys/bus/pci/devices/${1}/driver/unbind
+        if ! [ -w ${path} ]; then
+            echo "${prog}: Device ${1} not bound"
+            return 1
+        fi
+        echo -n ${1} >${path}
+    }
+
+    pcibind() {
+        local path
+        path=/sys/bus/pci/drivers/${2}/bind
+        if ! [ -w ${path} ]; then
+            echo "${prog}: Driver ${2} not found"
+            return 1
+        fi
+        echo ${1} >${path}
+    }
+
+    pciunbind ${BDF}
+    pcibind ${BDF} e1000e
+
+    dhclient
+
+TODO: describe how to run this at every startup
+
+Now configure your DHCP server so your testbench gets static IP and connect your machine to your local network. You should ensure that your testbench can reach the Internet.
+
+Install `openssh-server` on your testbench:
+
+``` {.wiki}
+yum install openssh-server
+```
+
+Ensure that sudo works without password from your user account (it should by default).
+
+Development VM
+--------------
+
+### SSH
+
+Arrange firewall so you can reach the testbench from your `qubes-dev` VM. Generate SSH key in `qubes-dev`:
+
+``` {.wiki}
+ssh-keygen -t ecdsa -b 521
+```
+
+Add the following section in `.ssh/config` in `qubes-dev`:
+
+``` {.wiki}
+Host testbench
+    # substitute username in testbench
+    User user
+    # substitute address of your testbench
+    HostName 192.168.123.45
+```
+
+Then connect to your testbench and paste newly generated `id_ecdsa` to `.ssh/authorized_keys` on testbench so you can log in without entering password every time.
+
+### Scripting
+
+This step is optional, but very helpful. Put these scripts somewhere in your `${PATH}`, like `/usr/local/bin`.
+
+`qtb-installrpm`:
+
+    #!/bin/sh
+
+    ssh testbench python -m qubes.tests.run
+
+`qtb-runtests`:
+
+    #!/bin/sh
+
+    if [ $# -ne 1 ]; then
+            echo "usage: $(basename $0) <rpmfile>"
+            exit 2
+    fi
+
+    scp ${1} testbench:/tmp/
+    ssh testbench sudo rpm -i --replacepkgs --replacefiles /tmp/"$(basename ${1})"
+
+`qtb-iterate`:
+
+    #!/bin/sh
+
+    set -e
+
+    # substitute path to your builder installation
+    pushd ${HOME}/builder >/dev/null
+
+    # the following are needed only if you have sources outside builder
+    #rm -rf qubes-src/core-admin 
+    #make COMPONENTS=core-admin get-sources
+
+    make core-admin
+    qtb-install qubes-src/core-admin/rpm/x86_64/qubes-core-dom0-2.1.64-1.fc20.x86_64.rpm
+    qtb-runtests
+
+### Hooking git
+
+I (woju) have those two git hooks. They ensure tests are passing (or are marked as expected failure) when commiting and pushing. For committing it is only possible to run tests that may be executed from git repo (even if the rest were available, I probably wouldn't want to do that). For pushing, I also install RPM and run tests on testbench.
+
+`core-admin/.git/hooks/pre-commit`: (you may retain also the default hook, here omitted for readability)
+
+    #!/bin/sh
+
+    set -e
+
+    python -c "import sys, qubes.tests.run; sys.exit(not qubes.tests.run.main())"
+
+`core-admin/.git/hooks/pre-push`:
+
+    #!/bin/sh
+
+    exec qtb-iterate