cf0b92f893
The idea on getTarget is to use kwargs to send custom variables to different targets, instead of this, a new variable was added (just used for custom targets) and this broke testexport. So in order to fix it, just add the custom variable to kwargs. This fixes the use of getTarget() in testexport class that was introduced in 1dc8010afd71fe46fb28bb86fb7c07a5fbd3d7cf. (From OE-Core rev: cf138029a1f18f991fc7a28c81d85884942e9d56) 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