Based on /meta-selftest/recipes-test/emptytest/emptytest.bb, manipulate this recipe so that, for example, it breaks during compile phase. See: https://wiki.yoctoproject.org/wiki/Oe-selftest#appending_to_a_recipe and meta/lib/oeqa/selftest/lic-checksum.py for details on how to manipulate the recipe. This can be used for bitbake/toaster/etc testing. Example of test: Basic test case that tries bitbaking the broken recipe and verifies that it fails in the expected way. This can be expanded with test on broken patching, broken web location for the tarball, etc. Another approach would be a fixed broken recipe that can be used for this kind of tests (one for each kind of test).
Why not create a selftest that would add some broken data into an existing recipe and try and build it?
This may fit into Daniel's work for bug 6370 (recipe testing). Basically this is the part where we add tests for bug 6370.
Moved to 2.5 due resources constraint
maybe still something to look in to ?
Added in oe-core 1810d4ab3374d833cb4b68388b456dc7ddb3d685.