Mariano Lopez c711caae83 oeqa/core/loader.py: Do not import underscore modules by default
Underscore modules are meant to be run only when manually added to the test
suite, so far another mechanisms are in place to make this happen with
runtime, sdk, and esdk (mostly in test* bbclasses).

This will add such functionality in the core framework so other specific
frameworks can take use this without adding something else.

[YOCTO #10980]

(From OE-Core rev: 2c6eac774768aa610a8b3784483b9e90fb629c2d)

Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-28 08:43:12 +01:00
..
2017-01-23 12:05:18 +00:00

= 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