Bug 10571 - create a Service Interface for the Automated Device Test Controller
Summary: create a Service Interface for the Automated Device Test Controller
Status: RESOLVED WONTFIX
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 10570
  Show dependency tree
 
Reported: 2016-11-01 21:00 UTC by Jair Gonzalez
Modified: 2018-11-06 14:46 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jair Gonzalez 2016-11-01 21:00:00 UTC
In order for external services or clients to be able to interact with the Automated Device Test Service, a Service Interface is required to define a set of methods to configure it, receive commands and respond accordingly using a RPC mechanism.
Comment 1 Benjamin Esquivel 2016-11-04 18:06:15 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
Comment 2 Richard Purdie 2018-11-06 14:46:31 UTC
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.