Bug 10580 - attach an html results page at the Autobulider's testing jobs
Summary: attach an html results page at the Autobulider's testing jobs
Status: RESOLVED DUPLICATE of bug 9678
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.4
Assignee: Plauchu Edwin
QA Contact:
URL:
Whiteboard:
Depends on: 9997
Blocks:
  Show dependency tree
 
Reported: 2016-11-01 22:54 UTC by Benjamin Esquivel
Modified: 2017-12-06 17:13 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments
xml sample output (10.00 KB, application/x-tar)
2016-11-03 22:10 UTC, Benjamin Esquivel
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Esquivel 2016-11-01 22:54:26 UTC
For better visualization of the results already posted at the autobuilder testing jobs, and taking into account that these already publish an XML of the test results, it is easy to parse them to an HTMLand provide a link to it in the AB task list.

The proposal is also to create the HTML template that will be populated with the results with some capabilities. These capabilities are:

- search substrings of the test name
- ability to filter by test result (passed/failed)
- log links at the failed tests

This could also shape the Test Report Tool's design and functionality since this is a playground for TRT features.
Comment 1 Benjamin Esquivel 2016-11-03 22:10:31 UTC
Created attachment 3524 [details]
xml sample output

The sample xml output attached is the result of running:

$ oe-selftest -r bbtests

it contains 2 failures and the rest passed. In total 25 tests run.
Comment 2 Leonardo Sandoval Gonzalez 2017-01-25 16:45:47 UTC
M2 missed, pushing the target to M3.
Comment 3 Leonardo Sandoval Gonzalez 2017-06-02 19:45:38 UTC
A generic mechanism will be created to see the results in testopia.

*** This bug has been marked as a duplicate of bug 9678 ***