aboutsummaryrefslogtreecommitdiffstats
path: root/chapter04/abouttestsuites.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter04/abouttestsuites.xml')
-rw-r--r--chapter04/abouttestsuites.xml6
1 files changed, 5 insertions, 1 deletions
diff --git a/chapter04/abouttestsuites.xml b/chapter04/abouttestsuites.xml
index 9fea71799..aca364c96 100644
--- a/chapter04/abouttestsuites.xml
+++ b/chapter04/abouttestsuites.xml
@@ -7,6 +7,9 @@
<title>About the test suites</title>
<?dbhtml filename="abouttestsuites.html"?>
+<para>See testing</para>
+
+<!--
<para>Most packages provide a test suite. Running the test suite for a newly
built package is generally a good idea, as it can provide a nice sanity check
that everything compiled correctly. A test suite that passes its set of checks
@@ -14,7 +17,7 @@ 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 -- GCC, Binutils, and Glibc -- are of
+suites for the core toolchain packages - GCC, Binutils, and Glibc - are of
the utmost importance due to their central role in a properly functioning
system. But be warned, the test suites for GCC and Glibc can take a very long
time to complete, especially on slower hardware.</para>
@@ -40,5 +43,6 @@ more detail later on in <xref linkend="chapter-temporary-tools"/>.</para>
<para>Sometimes package test suites will give false failures. You can
consult the LFS Wiki at <ulink url="&wiki-root;"/> to verify that these
failures are normal. This applies to all tests throughout the book.</para>
+-->
</sect1>