From 7a5685ad740f81e16bd92eb8196bdb4b5d41fd24 Mon Sep 17 00:00:00 2001 From: Mikko Rapeli Date: Wed, 30 Nov 2022 17:15:16 +0200 Subject: common-tasks.rst: fix oeqa runtime test path It's "runtime/cases" in master and kirkstone. If layer specific tests are in "runtime" directory, they will not be found. (From yocto-docs rev: 23dcf002eec5136427554112af8679fc2b98e61d) Signed-off-by: Mikko Rapeli Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/dev-manual/common-tasks.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'documentation') diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst index fbe8a29896..65f94432ab 100644 --- a/documentation/dev-manual/common-tasks.rst +++ b/documentation/dev-manual/common-tasks.rst @@ -8901,21 +8901,21 @@ You can start the tests automatically or manually: bitbake -c testimage image -All test files reside in ``meta/lib/oeqa/runtime`` in the +All test files reside in ``meta/lib/oeqa/runtime/cases`` in the :term:`Source Directory`. A test name maps directly to a Python module. Each test module may contain a number of individual tests. Tests are usually grouped together by the area tested -(e.g tests for systemd reside in ``meta/lib/oeqa/runtime/systemd.py``). +(e.g tests for systemd reside in ``meta/lib/oeqa/runtime/cases/systemd.py``). You can add tests to any layer provided you place them in the proper area and you extend :term:`BBPATH` in the ``local.conf`` file as normal. Be sure that tests reside in -``layer/lib/oeqa/runtime``. +``layer/lib/oeqa/runtime/cases``. .. note:: Be sure that module names do not collide with module names used in - the default set of test modules in ``meta/lib/oeqa/runtime``. + the default set of test modules in ``meta/lib/oeqa/runtime/cases``. You can change the set of tests run by appending or overriding :term:`TEST_SUITES` variable in @@ -9008,7 +9008,7 @@ Writing New Tests As mentioned previously, all new test files need to be in the proper place for the build system to find them. New tests for additional functionality outside of the core should be added to the layer that adds -the functionality, in ``layer/lib/oeqa/runtime`` (as long as +the functionality, in ``layer/lib/oeqa/runtime/cases`` (as long as :term:`BBPATH` is extended in the layer's ``layer.conf`` file as normal). Just remember the following: -- cgit v1.2.3-54-g00ecf