Correct manipulation of the task library is currently tested only indirectly, either through uploading and upgrading tasks through the web UI, or through the scheduling of jobs. This has resulted in a number of regressions making it through to the development branch or even all the way to production. With the new abstraction broken out as bkr.server.model.TaskLibrary, unit tests should be added that ensure correct operation (including filesystem manipulation and metadata generation) at the method level, independent of the rest of Beaker.
It would also be desirable to have RPM generation infrastructure in the test suite that supports creation of a valid RPM file for arbitrary tasks (see comments on http://gerrit.beaker-project.org/#/c/1958)
http://gerrit.beaker-project.org/#/c/2225/
Unit tests, so upgrading MODIFIED -> VERIFIED
Beaker 0.15 has been released.