8332 2015-09-18 17:02:21 +0000 QA: Add a broken recipe for testing purposes 2020-01-30 16:23:58 +0000 1 1 10 QA/Testing Build Testing general 5.99 x86 Multiple RESOLVED FIXED Medium enhancement Future 6370 1 cristian.iorga ross.burton akuster benjamin.esquivel bogdanx.a.voiculescu georgex.l.musat jose.perez.carranza joshuagloe randy.macleod ross.burton apoorv.sangal --- --- No (bug/feature does not impact docs) oldest_to_newest 54294 0 cristian.iorga 2015-09-18 17:02:21 +0000 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). 54619 1 georgex.l.musat 2015-09-24 14:28:14 +0000 Why not create a selftest that would add some broken data into an existing recipe and try and build it? 58724 2 alexandru.c.georgescu 2016-02-08 13:40:01 +0000 This may fit into Daniel's work for bug 6370 (recipe testing). Basically this is the part where we add tests for bug 6370. 76343 3 jose.perez.carranza 2017-08-30 15:51:48 +0000 Moved to 2.5 due resources constraint 85931 4 akuster 2019-12-22 20:39:42 +0000 maybe still something to look in to ? 86200 5 ross.burton 2020-01-30 16:23:58 +0000 Added in oe-core 1810d4ab3374d833cb4b68388b456dc7ddb3d685.