[OE-core] oe-selftest developer oriented improvements

[Stoicescu, CorneliuX]

> > 1)   Testing recipes updates or new recipes
> >
> > Even though we cannot test every single scenario or the functionality of a
> recipe, we could create a test suite that would:
> > - build the recipe with all major architectures(qemux86, qemux86-64,
> > qemuarm, qemuppc, qemumips)
> > - rebuild the recipe from sstate(with or without a sstate file for the
> > recipe)
> > - perform cleaning operations on the recipe(cleansstate)
> > - force all major tasks on the recipe (bitbake -C <task> <recipe>)
> > - selectively use each combination of .bbappend files with the recipe; all
> the combinations should not break the recipe build.
> > - we could also create mini test suites just for some of these tests like
> testing only the rebuild from sstate.
> > (any experience from common recipe build fails can be helpful here)
> >
> 
> I'd really like to see this, it could cut down on cases where something works
> for one developer but then hits an edge case when sent to the autobuilder.
> 
> I can also see 'type=package' being useful, to check that a generated
> package installs cleanly in an image. For example, if package x contains a file
> which clashes with something already installed on core-image-minimal,
> 'bitbake x' won't show this but 'bitbake core-image-minimal' with
> 'IMAGE_INSTALL += x' set will do.
> 
> Taking that a step further, that image could then be booted in qemu and the
> relevant ptest suite ran. I'm not sure how that would be automated myself or
> how the ptest log and results would be pulled off the qemu image but if it is
> possible I think it would be a very useful option.

Even though we cannot boot the image and run ptest at the moment using oe-selftest, it could be done in the future. This can be done now with the 'testimage' feature though. We need to investigate the usage of the 2 tools together.

Thank you for the feedback!

Regards,
Corneliu 
Yocto QA