Hey, we want Node to be a stable base OS, as node becomes bigger and complex it might be time to introduce some automated testing to different parts of node. The testing can start at real low-level stuff like syntax checks and unit tests, but should end in testing the whole process, so covering the installation, configuration and running some VMs. The testing itself can then be triggered at different points, e.g. syntax checks by using git-hooks, unit and sanity checks by e.g. jenkins or gerrit.
Open questions remain, like: When can we do reliable unit tests? Some TUI backing code relies on runtime informations (e.g. network informations) and thus can only be tested on a running node. - Or: How can we do automated testing of the TUI? An idea is to minimize the logic within the TUI code and to push all the logic into functions which then in turn can be tested. - And: How can the runtime sanity checks be run? I've written down the current plan on http://ovirt.org/wiki/Node_Testing which is far from complete, but a starting point. So, go ahead and add your comments, ideas, remarks, and questions to the wiki, to get machines to do all the testing for us :) Greetings fabian _______________________________________________ node-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/node-devel
