Hey, currently CI tests are run nightly on the master branch (with sometimes additional patches) and the results are posted to the node-patches ml.
The tests (currently the basic_tui testsuite) are run internally but the testcases itself are now kept in oVirt's gerrit [1, 2]. Some initial ideas of how to improve and what testcases to add to the testsuites are summarized in the wiki [3]. The testcases outlined there are just the basics, if you got a special testcase you want to cover, you are welcome to contribute a testcase and get it reviewed. This way you will get an nightly automated testing of your special testcase (which should be relevant to oVirt Node) "for free" :) It is even possible to do TUI testing by writing appropriate testcases [4] and using the provided common.input [5] python library (which builds upon uinput). There is also an example provided: [6] There is still work to do: The wiki pages need to be reorganized and cleaned up a bit. Additionall testcases can be written (like for the TUI, or TUI installation), … Greetings fabian -- [1] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git [2] http://gerrit.ovirt.org/#/q/status:open+project:ovirt-node-tests,n,z [3] http://ovirt.org/wiki/Node_Testing#Basic_Testcases [4] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git;a=blob; f=docs/Writing_TUI_Tests.rst;hb=HEAD [5] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git;a=tree; f=libs/common;hb=HEAD [6] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git;a=blob; f=tcs/uinput_login_as_admin.py;hb=HEAD
signature.asc
Description: This is a digitally signed message part
_______________________________________________ node-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/node-devel
