From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [nanbield][PATCH 20/20] test-manual: use working example
Date: Mon, 18 Dec 2023 22:33:34 +0100 [thread overview]
Message-ID: <20231218213334.146370-21-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20231218213334.146370-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
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 c79dfb6ab0..c31fd11c7a 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 <https://docs.python.org/3/library/unittest.html>`__.
--
2.34.1
prev parent reply other threads:[~2023-12-18 21:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:33 [nanbield][PATCH 00/20] Documentation backports michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 01/20] migration-guides: release 3.5 is actually 4.0 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 02/20] contributor-guide: fix command option michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 03/20] contributor-guide: add License-Update tag michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 04/20] dev-manual: layers: update link to YP Compatible form michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 05/20] migration-guide: add release notes for 4.2.4 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 06/20] ref-manual: releases.svg: update nanbield release status michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 07/20] manuals: fix URL michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 08/20] migration-guide: add release notes for 4.0.14 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 09/20] ref-manual: Fix reference to MIRRORS/PREMIRRORS defaults michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 10/20] dev-manual: Discourage the use of SRC_URI[md5sum] michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 11/20] test-manual: text and formatting fixes michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 12/20] test-manual: resource updates michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 13/20] test-manual: add links to python unittest michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 14/20] test-manual: explicit or fix file paths michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 15/20] test-manual: add or improve hyperlinks michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 16/20] migration-guides: reword fix in release-notes-4.3.1 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 17/20] manuals: brief-yoctoprojectqs: align variable order with default local.conf michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 18/20] dev-manual: runtime-testing: fix test module name michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 19/20] migration-guides: add release notes for 4.0.15 michael.opdenacker
2023-12-18 21:33 ` michael.opdenacker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231218213334.146370-21-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).