A test reporting tool is necessary for the various components that produce results. An example requirements of why such tool is needed are: i. the ability to store results from multiple sources (performance, manual, automated) ii. the ability to compare results with a tool that is designed for that purpose. Including comparing performance results which are trickier than functional testing iii. the centralization of the test result storage to allow a number of things like back up, replication, extension, advanced filtering, etc. These are just some of the benefits of having a tool for reporting. A wiki is proposed for the plan description: https://wiki.yoctoproject.org/wiki/QA/Test_Reporting_Tool Note that this is not intended to replace testopia as a test manager but to extend the testing capabilities by having a one stop shop for test reporting.
Hi Benjamin, The current work on the project mentioned in this enhancement is available in GitHub at: https://github.com/fullvlad/CustomReports
Thanks Alex, I believe that would be a valuable input
Ideally this tool would be able to consume, and compare, other quality related datasources such as the buildhistory from the autobuilder[1] and performance statistics. 1. http://git.yoctoproject.org/cgit/cgit.cgi/poky-buildhistory/
an initial set of requirements are written at this section: https://wiki.yoctoproject.org/wiki/QA/Test_Reporting_Tool#General_Expectations
The plan was written in the following bugs: - bug 9954, - bug 9956, - bug 9957, - bug 9958
Test Plan Created at https://wiki.yoctoproject.org/wiki/QA/Test_Reporting_Tool