| Summary: | oeqa: core add support to publish results | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Aníbal Limón <anibal.limon> |
| Component: | general | Assignee: | yeoh ee peng <ee.peng.yeoh> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | akuster, ee.peng.yeoh, joshuagloe, juan.m.cruz.alcaraz, leonardo.sandoval.gonzalez, markus.lehtonen, richard.purdie |
| Version: | 2.3 | ||
| Target Milestone: | 2.7 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Aníbal Limón
2017-05-25 20:53:56 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. This functionality should live in oe-core, we want to have less logic in the autobuilder where possible. 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) QA team is in process of creating a structure to store results and logs. Moving this to 2.6. 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 The autobuilder now generates testresults.json files. |