| Summary: | create a reporting module for the automated device test controller | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Jair Gonzalez <jair.de.jesus.gonzalez.plascencia> |
| Component: | general | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | richard.purdie |
| Version: | 2.3 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
| Bug Depends on: | |||
| Bug Blocks: | 10570 | ||
|
Description
Jair Gonzalez
2016-11-01 21:13:20 UTC
Setting these bugs to future as the testing service is not impacting the delivery of the functionality to the autobuilder flow. The autobuilder enabling of the hardware testing is being tracked in bug 10603 I'm not sure we (as a project) want to invent yet another automated test device system. We should therefore try and interface to one that already exists such as LAVA or one of the others. |