With the purpose that the Automated Device Test Service is able to track the inventory of devices that it's associated with it, and select and interact with those that are required, it becomes necessary to create a DUT Management component to store and control the associated DUT metadata.
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.