Yocto currently doesn't have much of a test framework, just the bare essentials it needs to do the runtime qemu testing. We continue to look at the various test frameworks out there (e.g. CATS, TI's framework) but we're really waiting for someone to step up and take ownership of this area. It needs some resource commitment as its not a simple task.
I'll just note here that I'm working on a framework called ptest for building, installing and running package tests on target. Description: https://lists.yoctoproject.org/pipermail/yocto/2012-June/009443.html Latest patch set: http://lists.linuxtogo.org/pipermail/openembedded-core/2012-November/032076.html
The ptest framework is now merged to master. Combined with the deployment of Testopia, I'd say we are a few steps closer to solving this bug.
I think we now have a much clearer plan here. We have testopia, we have ptest and we have the qemuimage test code. I'm going to mark this as resolved since we have specific bugs covering the work needed on the other items.
We now have the following: - Testopia tets case management platform: https://wiki.yoctoproject.org/wiki/Testopia - an automated reporting system: bug 3712 - package testing system (ptest): bug 4114 - build performance measurement: bug 3886 - selected autobuilder as QA autmation tool: bug 4137 - rework qemuimagetest implementation: bug 4435 Marking as Verified.