Bug 11583 - oeqa: core add support to publish results
Summary: oeqa: core add support to publish results
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.7 M1
Assignee: yeoh ee peng
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-05-25 20:53 UTC by Aníbal Limón
Modified: 2019-01-10 16:03 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aníbal Limón 2017-05-25 20:53:56 UTC
At this time oe-selftest has a functionality to publish test results into a git respository but isn't on use.

The implementation needs to be in OEQA core to share the functionality across Test components.
Comment 1 Aníbal Limón 2017-07-19 19:41:39 UTC
This is an old discussion, the oeqa framework needs to handle it? or the AutoBuilder when the results log comes?.

The oe-git-archive already has this functionality currently used by build performance tests.
Comment 2 Joshua Lock 2017-07-20 12:56:52 UTC
This functionality should live in oe-core, we want to have less logic in the autobuilder where possible.
Comment 3 Markus Lehtonen 2018-02-21 07:45:16 UTC
As scripts/oe-git-archive handles committing test results to git and pushing them upstream, this should be simple to implement as an autobuilder step. Virtually a one-liner running oe-git-archive (with the desired options)
Comment 4 Apoorv 2018-03-07 19:15:05 UTC
QA team is in process of creating a structure to store results and logs. Moving this to 2.6.
Comment 5 yeoh ee peng 2018-09-20 06:06:00 UTC
In order to allow easy consumption/analysis of the published testresult by future reporting tools, the published testresult need to have standard format and structure. 

Propose to enable oeqa to output testresult grouped by each module into separate json files with predefined structure (testsuite - testcase). 

Submitted the patch to openembedded-core mailing list. 
http://lists.openembedded.org/pipermail/openembedded-core/2018-September/155856.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-September/155855.html
Comment 6 Richard Purdie 2019-01-10 16:03:36 UTC
The autobuilder now generates testresults.json files.