If importing a test with the same name as a built-in module, it will silently import the built-in and check for tests in built-in module. This happened with syslog module in debian based machines, so add a raise to avoid this behavior. [YOCTO #10978] (From OE-Core rev: d9548f981448307b042807373e469f0d0b110bfe) Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
= OEQA Framework =
== Introduction ==
This is the new OEQA framework the base clases of the framework are in this module oeqa/core the subsequent components needs to extend this classes.
A new/unique runner was created called oe-test and is under scripts/ oe-test, this new runner scans over oeqa module searching for test components that supports OETestContextExecutor implemented in context module (i.e. oeqa/core/context.py).
For execute an example:
$ source oe-init-build-env $ oe-test core
For list supported components:
$ oe-test -h
== Create new Test component ==
Usally for add a new Test component the developer needs to extend OETestContext/OETestContextExecutor in context.py and OETestCase in case.py.
== How to run the testing of the OEQA framework ==
Run all tests:
$ PATH=$PATH:../../ python3 -m unittest discover -s tests
Run some test:
$ cd tests/ $ ./test_data.py