Report consumers usually take JUnit xml formatted output and the OeTest class is incapable of adding this support. The fact that OeTest uses the TextTestRunner, which is a sample implementation, makes it incompatible with the xmlrunner as it is a very limited design. A standard implementation of the unittest.main() instead of the TextTestRunner would easily allow to get the xml output. The proposal is to move away from the TextTestRunner in favor of unittest.main()
Created attachment 3302 [details] oe-selftest log with XML report generation
Created attachment 3303 [details] oe-selftest log with XML report functionality but NO library installed The attachment shows how oe-selftest log defaults to the no XML results reporting when the module is not installed. Keeping the previous functionality intact.
Created attachment 3304 [details] xml sample output Attaching sample XML output of 3 bitbake tests
Created attachment 3305 [details] pre and post xmlrunner text output collateral changes in the text output of oe-selftest listed at the attachment. This will be addressed with a different bug so it can be proposed at the xmlrunner code.
Review at: http://lists.openembedded.org/pipermail/openembedded-core/2016-July/124159.html
merged at: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/scripts/oe-selftest?id=e91d0d5d1c7e28c5b1272df2b749d92279183d8a