7848 2015-06-05 03:32:47 +0000 Support external TC manifest as the input of TEST_SUITES 2015-08-20 04:33:53 +0000 1 1 10 QA/Testing Runtime Testing general 1.8.1 x86 Multiple VERIFIED FIXED Medium+ enhancement 1.9 M1 1 cathy.shen costin.c.constantin alexandru.c.georgescu jing.j.wang junhuix.zhang cathy.shen --- --- Don't know oldest_to_newest 51517 0 cathy.shen 2015-06-05 03:32:47 +0000 Run a specific test case list flexibly by an manifest file, but not put the case names in TEST_SUITES value. There are two solutions, but the first one is much flexible and we'll have patch submitted to Yocto. 1. TEST_SUITES = "${@read_testlist("/some/file")}" 2. bitbake -r mytests.conf <other options> 51632 1 cathy.shen 2015-06-11 09:05:55 +0000 For "bitbake -r mytests.conf <other options>", the limitation is it depend on bitbake, and the mytests.conf is a bitbake specific format, we'd like to run exported test in the environment which might not have bitbake environment with more generic format, like manifest or json. So we prefer the solution "TEST_SUITES = "${@read_testlist("/some/file")}"" One more additional request for this ticket: Is it possible to support multiple manifest file as the input? We'd like this capability as well. Thanks! 52094 2 junhuix.zhang 2015-07-02 09:18:36 +0000 User can specify TESTSUITE by external files in local.conf, e.g. TEST_SUITES_MANIFEST = "test1.manifest test2.manifest". The files lie in build/conf/. TEST_SUITES_MANIFEST supports relative path(which relative to build/conf/) and absolute path. Although the way like TEST_SUITES = "${@read_testlist(d, "test1.manifest")" is also workable, per testing, it has performance issue because running a couple of times during BB parsing stage. 52324 3 cathy.shen 2015-07-14 06:04:44 +0000 Merged to poky master branch. Commit ID: 245899cc98881d2be784f8e7302120765c2bc7f 52327 4 cathy.shen 2015-07-14 06:08:03 +0000 verified with poky master branch.