A Task Scheduling component is required for Automated Device Test Service in order to prioritize testing tasks execution and distribute the workload between the available resources efficiently.
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.