![]() Those methods are used to write in the log the results so it makes sense to have defined at OETestResult because is a format of the result itself. [YOCTO #11450] (From OE-Core rev: 33a783f59ed4e232f41f8b09dfa7955f2ddc2f80) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
---|---|---|
.. | ||
cases | ||
decorator | ||
target | ||
tests | ||
utils | ||
__init__.py | ||
case.py | ||
context.py | ||
exception.py | ||
loader.py | ||
README | ||
runner.py |
= 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