Hey, after some time oVirt Node builds are finally also running through Igor [1] - a tool to do some continuous testing on VMs and real hardware.
Currently igor is doing a basic test, so testing if the automatic installation works and if the can reboot. This testing is done once each night and report is sent to the node-patches [2, 2a] mailing-list. Running the tests required some preparations to meet Node's requirements. Igor [1] can manage the lifetime of a test instance (or real server) and prepares cobbler to provision the instance. Afterwards it supervises the testing process and cleans everything when it reached it's EOL (by passing or failing the testcases). A client [3] is injected into the (build by Jenkins) ISO using jboggs plugin patches [4], which is executing all the necessary stuff on the Node. Now that the infrastructure is in place the next steps will be to add some testcases (structured into testsets and testsuites) to [5]. The testcases should cover automatic and TUI install, but further more we should even do unit tests on the underlying "libraries" (like ovirt-functions). This has to be done online, because most of the functions expect a running system. If you want to contribute testcases - or anything else - have a look at the examples in [1] and [2]. Greetings fabian -- [1] https://gitorious.org/ovirt/igord [2] http://lists.ovirt.org/pipermail/node-patches/ [2a] http://lists.ovirt.org/pipermail/node-patches/2012-June/001481.html [3] http://gerrit.ovirt.org/#/c/5460/ [4] https://gitorious.org/ovirt/ovirt-igor-client [5] https://gitorious.org/ovirt/ovirt-node-igor-testsuites
signature.asc
Description: This is a digitally signed message part
_______________________________________________ node-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/node-devel
