From 8b1909aa6f7a51a878dc3d4a9223403ad3e164a9 Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Thu, 5 Jan 2023 08:34:26 +0100 Subject: manuals: simplify references to classes Now that .bbclass is removed from class section titles. We can now have, for example, :ref:`ref-classes-insane` instead of :ref:`insane `. Then, when necessary, rework paragraphs so that they have lines of even length, not exceeding 80 characters. (From yocto-docs rev: e76190e3be78c1e483bec0469f1e437dbf8f3791) Signed-off-by: Michael Opdenacker Suggested-by: Quentin Schulz Signed-off-by: Richard Purdie --- documentation/test-manual/intro.rst | 18 +++++++++--------- documentation/test-manual/understand-autobuilder.rst | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-) (limited to 'documentation/test-manual') diff --git a/documentation/test-manual/intro.rst b/documentation/test-manual/intro.rst index 2d75e141f1..aaf64ae017 100644 --- a/documentation/test-manual/intro.rst +++ b/documentation/test-manual/intro.rst @@ -100,12 +100,11 @@ the following types of tests: different configurations, such as different init systems. The Autobuilder tests literally hundreds of configurations and targets. - - *Sanity Checks During the Build Process:* Tests initiated through - the :ref:`insane ` - class. These checks ensure the output of the builds are correct. - For example, does the ELF architecture in the generated binaries - match the target system? ARM binaries would not work in a MIPS - system! + - *Sanity Checks During the Build Process:* Tests initiated through the + :ref:`ref-classes-insane` class. These checks ensure the output of the + builds are correct. For example, does the ELF architecture in the + generated binaries match the target system? ARM binaries would not work + in a MIPS system! - *Build Performance Testing:* Tests whether or not commonly used steps during builds work efficiently and avoid regressions. Tests to time @@ -121,7 +120,8 @@ the following types of tests: $ bitbake image -c testsdkext - The tests utilize the :ref:`testsdkext ` class and the ``do_testsdkext`` task. + The tests utilize the :ref:`ref-classes-testsdk` 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 distributions @@ -131,7 +131,7 @@ the following types of tests: $ bitbake image -c testimage - The tests utilize the :ref:`testimage ` + The tests utilize the :ref:`ref-classes-testimage` class and the :ref:`ref-tasks-testimage` task. - *Layer Testing:* The Autobuilder has the possibility to test whether @@ -151,7 +151,7 @@ the following types of tests: $ bitbake image -c testsdk - The tests utilize the :ref:`testsdk ` class and + The tests utilize the :ref:`ref-classes-testsdk` class and the ``do_testsdk`` task. - *Unit Testing:* Unit tests on various components of the system run diff --git a/documentation/test-manual/understand-autobuilder.rst b/documentation/test-manual/understand-autobuilder.rst index b6e331f68c..7a6cb2443b 100644 --- a/documentation/test-manual/understand-autobuilder.rst +++ b/documentation/test-manual/understand-autobuilder.rst @@ -206,7 +206,7 @@ are general setup steps that are run once and include: #. Set up any :term:`buildtools` tarball if configured. -#. Call "buildhistory-init" if :ref:`buildhistory ` is configured. +#. Call "buildhistory-init" if :ref:`ref-classes-buildhistory` is configured. For each step that is configured in ``config.json``, it will perform the following: -- cgit v1.2.3-54-g00ecf