#110 Document the TAP13 structure required for resultsdb and bodhi comment reporting
Closed: Fixed None Opened 9 years ago by tflink.

Our documentation currently states that using libtaskotron.check.CheckDetail is the best way to generate report-able TAP13 but we're really light on the details for what that TAP13 is supposed to look like.

Document the required structure for TAP13 for it to be used for reporting, making sure to note:
* which keys are used for which fields in resultsdb/bodhi_comment
* any formatting restrictions (types for item_type, etc.)
* examples of valid TAP13


This ticket had assigned some Differential requests:
D253

Metadata Update from @tflink:
- Issue tagged with: easyfix

6 years ago

Login to comment on this ticket.

Metadata