aboutsummaryrefslogtreecommitdiffstats
path: root/meta-selftest/COPYING.MIT
diff options
context:
space:
mode:
authorStefan Stanacar <stefanx.stanacar@intel.com>2013-11-27 19:08:50 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-03 12:49:18 +0000
commit41a4f8fb005328d3a631a9036ceb6dcf75754410 (patch)
tree22fac4985f92fac1426188e0020ff5333f73cb86 /meta-selftest/COPYING.MIT
parent4a45a999e0ad2e99581428a5a6d34f483c00544f (diff)
downloadopenembedded-core-contrib-41a4f8fb005328d3a631a9036ceb6dcf75754410.tar.gz
openembedded-core-contrib-41a4f8fb005328d3a631a9036ceb6dcf75754410.tar.bz2
openembedded-core-contrib-41a4f8fb005328d3a631a9036ceb6dcf75754410.zip
scripts/oe-selftest: script to run builds as unittest against bitbake or various scripts
The purpose of oe-selftest is to run unittest modules added from meta/lib/oeqa/selftest, which are tests against bitbake tools. Right now the script it's useful for simple tests like: - "bitbake --someoption, change some metadata, bitbake X, check something" type scenarios (PR service, error output, etc) - or "bitbake-layers <...>" type scripts and yocto-bsp tools. This commit also adds some helper modules that the tests will use and a base class. Also, most of the tests will have a dependency on a meta-selftest layer which contains specially modified recipes/bbappends/include files for the purpose of the tests. The tests themselves will usually write to ".inc" files from the layer or in conf/selftest.inc (which is added as an include in local.conf at the start and removed at the end) It's a simple matter or sourcing the enviroment, adding the meta-selftest layer to bblayers.conf and running: oe-selftest to get some results. It would finish faster if at least a core-image-minimal was built before. [ YOCTO #4740 ] Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-selftest/COPYING.MIT')
0 files changed, 0 insertions, 0 deletions