Changeset db083a3

Timestamp:

May 17, 2014, 9:50:36 PM (11 years ago)

Author:

Chris Staub <chris@…>

Branches:

clfs-3.0.0-systemd, master, systemd

Children:

6eb13f4

Parents:

8b8c815

git-author:

Chris Staub <chris@…> (05/17/14 21:50:17)

git-committer:

Chris Staub <chris@…> (05/17/14 21:50:36)

Message:

Reworded test suite pages

Location:

BOOK

Files:

• final-preps/abouttestsuites.xml (modified) (1 diff)
• final-system/common/testsuitesagain.xml (modified) (1 diff)

BOOK/final-preps/abouttestsuites.xml

@@ -11 +11 @@
   <title>About the Test Suites</title>
 
-  <para>Most packages provide a test suite. Running the test suite for a
-  newly built package is a good idea because it can provide a <quote>sanity
-  check</quote> indicating that everything compiled correctly. A test suite
-  that passes its set of checks usually proves that the package is
-  functioning as the developer intended. It does not, however, guarantee
-  that the package is totally bug free.</para>
-
-  <para>It is not possible to run testsuites when cross-compiling, so package installation instructions do not explain how to run testsuites until <xref linkend="chapter-building-system"/>.</para>
+  <para>Most packages provide a test suite, usually a script or
+  <command>make</command> target, which tests the just-compiled programs or
+  libraries by executing or linking to them. Test suites are often useful
+  for verifying that a package compiled correctly. However, they cannot
+  be run while cross-compiling so we will not mention test suite commands
+  for any packages until <xref linkend="chapter-building-system"/>.</para>
 
 </sect1>

BOOK/final-system/common/testsuitesagain.xml

@@ -12 +12 @@
 
   <para>In the final-system build, you are no longer cross-compiling so it
-  is possible to run package testsuites. Some test suites are more important
-  than others. For example,  the test suites for the core toolchain
-  packages&mdash;GCC, Binutils, and Glibc&mdash;are of the utmost
+  is possible to run package testsuites. Running the test suite for a
+  newly built package is a good idea because it can provide a <quote>sanity
+  check</quote> indicating that everything compiled correctly. A test suite
+  that passes its set of checks usually proves that the package is
+  functioning as the developer intended. It does not, however, guarantee
+  that the package is totally bug free.</para>
+
+  <para>Some test suites are more important than others. For example, the test
+  suites for the core toolchain packages&mdash;GCC, Binutils,
+  and Glibc&mdash;are of the utmost
   importance due to their central role in a properly functioning system.
   The test suites for GCC and Glibc can take a very long time to complete,