For automating runtime testing on different devices as MinnowBoard, Galileo, etc. it becomes necessary to create a control service that receives requests for testing an image on a single device or on a group of devices, and handles their initialization; image flashing; task queuing and scheduling; load, execution and monitoring of the tests; and test run results reporting. This service will leverage the existing Python library DevAuto in conjunction with the AFT (Automated Flasher Tester - https://github.com/skuusela/AFT) effort in order to interact with the actual devices, to flash the target images on them and make them ready for the testing process. This is a master bug and it'll serve as reference bug for tracking the development of the parts involved.
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
Waiting for: https://elinux.org/Automated_Testing_Summit to decide if this enhancement should be kept.
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.