linux/poky.git/meta/lib/oeqa/selftest/base.py, branch hardknott

oeqa/selftest: Move base class to case module

2017-06-06T18:02:43+00:00

To match the new structure of the OEQA framework. (From OE-Core rev: 0d3d97414c8166d09065f6f7f45e3260ce405692) Signed-off-by: Leonardo Sandoval Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

base.py: add assertExists and assertNotExists to oeselftest

2017-05-25T22:59:31+00:00

Current osselftest print confusing assertion message when using self.assertTrue(os.path.exists(filepath)) to test file path, example of confusing assertion message: AssertionError: False is not true Add the assertExists and assertNotExists to improve assertion message and simplify coding, using selft.assertExists(filepath), will print meaningful assertion message: AssertionError: does not exist [YOCTO #11356] (From OE-Core rev: b0a74554ef926ce05078494ca8e67178b56232f5) Signed-off-by: Yeoh Ee Peng Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

selftest: remove extra backslashes from debug output

2017-03-08T11:52:56+00:00

Remove unneeded backslashes from the format strings that caused debug output to look confusing: 2017-03-06 16:52:42,428 - selftest.base - DEBUG - Removing from: ... \IMAGE_FSTYPES = "wic" WKS_FILE = "mkefidisk.wks" (From OE-Core rev: 6b7f8f81307720b0a6c1ef4af5200dec9b8ef789) Signed-off-by: Ed Bartosh Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

selftest/base: don't fetch DISTRO variable in constructor

2017-01-16T18:05:14+00:00

Fetching the DISTRO variable in the base constructor means that we have to start bitbake for every test case instance, which adds minutes to the startup time. (From OE-Core rev: ac1c118dcb3cb27807b55115ef274a92bb512dd6) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

selftest: base: new object member to store the DISTRO value

2016-12-16T10:23:22+00:00

Instead of quering it multiple times, query once and use it on test method skip checks. Also, rename current distro sstate object member to a more meaninful name. (From OE-Core rev: bde9d99575a63ad2d7fd5974ce6ce19aad9a8984) Signed-off-by: Leonardo Sandoval Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa/selftest/base: backup and restore local configuration files

2016-09-23T13:56:39+00:00

Selftests' cleanup method during test setup is not capable of restoring local configuration files that remain modified after aborting a test through a keyboard interruption. This change creates backups for local.conf and bblayers.conf at test setup, restore them when found, and deletes them at cleanup. [YOCTO #9390] (From OE-Core rev: 0877278e07e4c2494c4c23199490dc47a5cee69d) Signed-off-by: Jose Lamego Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta/selftest/scripts: Use print function for python3 compatibility

2016-05-21T21:26:32+00:00

Used print function instead of print statement to make the code work in python 3. [Changes from both Ed and Richard] (From OE-Core rev: ced1995694c394d92cb82fb9c25a33dc027a3b69) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

lib/oeqa/selftest/base.py: Correct a reference to meta/lib/oeqa/selftest

2016-04-18T15:28:22+00:00

(From OE-Core rev: 4ed2a6d43ea19a3026d94666fc342493689d7d46) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

scripts/oe-selftest: Allow to run tests on random/all MACHINEs

2016-01-07T13:40:17+00:00

Add an option for random MACHINE into oe-selftest: --machine [random/all] 1. random: will set a random MACHINE for each test 2. all: will run tests for all machines Custom machine sets only weak default values (??=) for MACHINE in machine.inc. This let test cases that require a specific MACHINE to be able to override it, using (?= or =). e.g.: oe-selftest --run-tests signing --machine random --> will run all tests switching MACHINE randomly for each test oe-selftest --run-tests signing --machine all --> for each machine will run all tests oe-selftest --run-all-tests --machine random Also update oeqa/selftest/base.py to accomodate this feature. Fix for [YOCTO #5880]. (From OE-Core rev: 4a9c3653eecd9a3c1b45bab5e16c8d679c55f8bd) Signed-off-by: Daniel Istrate Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa/selftest: clean up selftest.inc in teardown

2015-10-21T21:56:07+00:00

Test cases may want to do call bitbake in setUpClass() but at that point the previous selftest.inc is still present which could change the build configuration and result in any built artifacts being removed in the next bitbake invocation as part of the sysroot clean up. Resolve this by cleaning selftest.inc in the tearDown, the clean in setUp should be considered a safety net. (From OE-Core rev: 573bd03a7844a5ad762533f65f41214df31cd197) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie