Bug 8332

Summary: QA: Add a broken recipe for testing purposes
Product: [QA/Testing] Build Testing Reporter: Cristian Iorga <cristian.iorga>
Component: generalAssignee: Ross Burton <ross.burton>
Status: RESOLVED FIXED QA Contact: Apoorv <apoorv.sangal>
Severity: enhancement    
Priority: Medium CC: akuster, benjamin.esquivel, bogdanx.a.voiculescu, georgex.l.musat, jose.perez.carranza, joshuagloe, randy.macleod, ross.burton
Version: 5.99   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 6370    

Description Cristian Iorga 2015-09-18 17:02:21 UTC 
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).
Comment 1 Lucian Musat 2015-09-24 14:28:14 UTC 
Why not create a selftest that would add some broken data into an existing recipe and try and build it?
Comment 2 Alexandru Georgescu 2016-02-08 13:40:01 UTC 
This may fit into Daniel's work for bug 6370 (recipe testing).
Basically this is the part where we add tests for bug 6370.
Comment 3 Jose Perez C 2017-08-30 15:51:48 UTC 
Moved to 2.5 due resources constraint
Comment 4 Armin Kuster 2019-12-22 20:39:42 UTC 
maybe still something to look in to ?
Comment 5 Ross Burton 2020-01-30 16:23:58 UTC 
Added in oe-core 1810d4ab3374d833cb4b68388b456dc7ddb3d685.