From 51c390571f32642333a910e7623b02d25ab5730f Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Wed, 6 Dec 2023 16:42:23 +0100 Subject: test-manual: use working example (From yocto-docs rev: 29dce8130e4de68a4690add673bca0eef17c8260) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/test-manual/intro.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/test-manual/intro.rst b/documentation/test-manual/intro.rst index d14aa20f76..e72a51172c 100644 --- a/documentation/test-manual/intro.rst +++ b/documentation/test-manual/intro.rst @@ -195,15 +195,15 @@ Tests map into the codebase as follows: Use this option when you wish to skip tests that access the network, which are mostly necessary to test the fetcher modules. To specify individual test modules to run, append the test module name to the - "bitbake-selftest" command. For example, to specify the tests for the - bb.data.module, run:: + ``bitbake-selftest`` command. For example, to specify the tests for + ``bb.tests.data.DataExpansions``, run:: - $ bitbake-selftest bb.test.data.module + $ bitbake-selftest bb.tests.data.DataExpansions You can also specify individual tests by defining the full name and module plus the class path of the test, for example:: - $ bitbake-selftest bb.tests.data.TestOverrides.test_one_override + $ bitbake-selftest bb.tests.data.DataExpansions.test_one_var The tests are based on `Python unittest `__. -- cgit v1.2.3-54-g00ecf