Bug 6988

Summary: Add a populate_sdk_test task
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Robert Yang <liezhi.yang>
Component: devtools / tool chainAssignee: Robert Yang <liezhi.yang>
Status: VERIFIED FIXED QA Contact: Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu>
Severity: enhancement    
Priority: Medium CC: bluelightning, bogdanx.a.voiculescu, mark.hatle, meta.mr.watcher, meta.watcher, richard.purdie, sgw
Version: 1.8   
Target Milestone: 1.9   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Robert Yang 2014-11-21 02:42:18 UTC 
The populate_sdk_test is used for sanity test after the sdk is built from the DEV side, we usually build the SDK, but don't know whether it works or not from the DEV side, when the QA team reports the problem, then we need pay a few time to reproduce and fix it, we can add a task like populate_sdk_test (or other names) to test the sdk after it is generated, and find the problem as early as possible rather than delay it to the QA team.

The basic design is:
1) addtask populate_sdk_test after populate_sdk
2) The populate_sdk_test will install the sdk and run some test cases when SDKMACHINE is the same as the build host, if not, then skip the test and warning.
3) We need the ability to add the testcases to populate_sdk_test
Comment 1 Paul Eggleton 2015-03-18 17:00:23 UTC 
We added support for this in 1.7 I believe - see meta/classes/testimage.bbclass - the tests (only one or two now) are in meta/lib/oeqa/sdk/. It looks to me like we cover everything mentioned in the bug report so I'm marking this as resolved; if that's not correct we can reopen but for any major enhancements we probably would be better off opening new ones.
Comment 2 Bogdan Alexandru Voiculescu 2015-09-08 07:29:06 UTC 
Verified: task is do_testsdk and are running on AB after 8084 was implemented.