From c643a4749c436baeb6943fe960f77a48deaef8e5 Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Tue, 23 Mar 2021 17:58:45 +0100 Subject: manuals: Spellcheck and capitalization fixes - Spelling fixes found using Emacs' spelling checker configured for US English - Fixes for some capitalization issues, especially some project names (QEMU, openSUSE, BusyBox), that were not consistently used with the same capitalization anyway. - A few whitespace fixes too (From yocto-docs rev: 05d69f17490dcc4933dcd85e57d9db53b912084a) Signed-off-by: Michael Opdenacker Reviewed-by: Nicolas Dechesne Signed-off-by: Richard Purdie --- documentation/test-manual/intro.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'documentation/test-manual/intro.rst') diff --git a/documentation/test-manual/intro.rst b/documentation/test-manual/intro.rst index 81c24a8c3f..101d283665 100644 --- a/documentation/test-manual/intro.rst +++ b/documentation/test-manual/intro.rst @@ -26,7 +26,7 @@ engineers: - *yocto-autobuilder2:* This :yocto_git:`README.md ` - is the main README which detials how to set up the Yocto Project + is the main README which details how to set up the Yocto Project Autobuilder. The ``yocto-autobuilder2`` repository represents the Yocto Project's console UI plugin to Buildbot and the configuration necessary to configure Buildbot to perform the testing the project @@ -88,7 +88,7 @@ Yocto Project Tests - Types of Testing Overview =============================================== The Autobuilder tests different elements of the project by using -thefollowing types of tests: +the following types of tests: - *Build Testing:* Tests whether specific configurations build by varying :term:`MACHINE`, @@ -124,7 +124,7 @@ thefollowing types of tests: The tests utilize the ``testsdkext`` class and the ``do_testsdkext`` task. - *Feature Testing:* Various scenario-based tests are run through the - :ref:`OpenEmbedded Self test (oe-selftest) `. We test oe-selftest on each of the main distrubutions + :ref:`OpenEmbedded Self test (oe-selftest) `. We test oe-selftest on each of the main distributions we support. - *Image Testing:* Image tests initiated through the following command:: @@ -474,7 +474,7 @@ correctly. The test would only run if python3 is installed in the SDK. ---------------------- The performance tests usually measure how long operations take and the -resource utilisation as that happens. An example from +resource utilization as that happens. An example from ``meta/lib/oeqa/buildperf/test_basic.py`` contains the following:: class Test3(BuildPerfTestCase): @@ -524,5 +524,5 @@ This is particularly true for oe-selftests since these can run in parallel and changing metadata leads to changing checksums, which confuses BitBake while running in parallel. If this is necessary, copy layers to a temporary location and modify them. Some tests need to -change metadata, such as the devtool tests. To prevent the metadate from +change metadata, such as the devtool tests. To protect the metadata from changes, set up temporary copies of that data first. -- cgit v1.2.3-54-g00ecf