66f536ad57
The logger handling in oeqa was confused at best. This patch: a) Passes in a logger through various qemu runner pieces b) Uses that logger consistently in the code c) Creates a logger for QemuRunner outside the bitbake namespace meaning we don't conflict with the tinfoil logging changes The result of this is more consistency. For runtime tests in testimage, the logs always contain the debug info, nothing is shwon on the console. For the oe-selftests, logs are intercepted and only shown if the test fails. (From OE-Core rev: ba8babc45141891d0624f9a181a580fa416e87ec) (From OE-Core rev: 22003f97ff7f53c32999dc466d26c1471ead9b6b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
---|---|---|
.. | ||
cases | ||
decorator | ||
target | ||
tests | ||
utils | ||
README | ||
__init__.py | ||
case.py | ||
context.py | ||
exception.py | ||
loader.py | ||
runner.py |
README
= 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