Test reports template
Suggestions on layout
I would suggest to have a high-level component main page where all the links to the reports relative to the single patches are kept.
Content
For each patch you certify you should produce a report. The report should contain several sections
- a set up section: a brief description of what you did to install the necessary component, and if relevant, in what way it differs from a standard YAIM installation, in other words what are the additional manual steps to reproduce your set up.
- a section for the "general" tests
- a section for the tests related to the bugs attached to the patch.
For the section on the "general tests":
- a copy and paste of the output observed when the running the certification test suite component, when available
- a copy and paste of the output observed when the running the regression tests test suite component, when available
- a short description of any manual tests performed and their results (copy and paste of the commands or a screenshot will do)
For the section on the tests related to the bugs attached to the patch, ideally for each bug you should
- if you do not plan to reproduce it nor test it, describe with a sentence why
- if you plan to reproduce it, then you should cover
- if applicable, the steps you did to reproduce the conditions in which the bug was experienced
- the tests done
- the outcome of your tests
Examples
See for reference the CREAM and CREAMCLI reports
--
DianaBosio - 24 Mar 2009