We need to add some manual test cases to better test the eSDK artefacts generated during a release, we have had issues reported in the past with the generated artefacts and therefore we need to design some tests to try and prevent such failures in future release.

Brian; could you provide some more background/context on the failures we've seen in the past?

The test case should exercise real-world usage patterns, including installation of additional features (from the yp.o sstate mirror). In #11963 Brian suggested "The linux kernel workflow is a good test since it is how a number of users will leverage the esdk in the next release given our new kernel documentation."

Kernel documentation is http://www.yoctoproject.org/docs/2.4/kernel-dev/kernel-dev.html and the eSDK workflow should be easy to follow.