Changeset db083a3


Ignore:
Timestamp:
May 17, 2014, 9:50:36 PM (6 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/2014 09:50:17 PM)
git-committer:
Chris Staub <chris@…> (05/17/2014 09:50:36 PM)
Message:

Reworded test suite pages

Location:
BOOK
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • BOOK/final-preps/abouttestsuites.xml

    r8b8c815 rdb083a3  
    1111  <title>About the Test Suites</title>
    1212
    13   <para>Most packages provide a test suite. Running the test suite for a
    14   newly built package is a good idea because it can provide a <quote>sanity
    15   check</quote> indicating that everything compiled correctly. A test suite
    16   that passes its set of checks usually proves that the package is
    17   functioning as the developer intended. It does not, however, guarantee
    18   that the package is totally bug free.</para>
    19 
    20   <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>
     13  <para>Most packages provide a test suite, usually a script or
     14  <command>make</command> target, which tests the just-compiled programs or
     15  libraries by executing or linking to them. Test suites are often useful
     16  for verifying that a package compiled correctly. However, they cannot
     17  be run while cross-compiling so we will not mention test suite commands
     18  for any packages until <xref linkend="chapter-building-system"/>.</para>
    2119
    2220</sect1>
  • BOOK/final-system/common/testsuitesagain.xml

    r8b8c815 rdb083a3  
    1212
    1313  <para>In the final-system build, you are no longer cross-compiling so it
    14   is possible to run package testsuites. Some test suites are more important
    15   than others. For example,  the test suites for the core toolchain
    16   packages&mdash;GCC, Binutils, and Glibc&mdash;are of the utmost
     14  is possible to run package testsuites. Running the test suite for a
     15  newly built package is a good idea because it can provide a <quote>sanity
     16  check</quote> indicating that everything compiled correctly. A test suite
     17  that passes its set of checks usually proves that the package is
     18  functioning as the developer intended. It does not, however, guarantee
     19  that the package is totally bug free.</para>
     20
     21  <para>Some test suites are more important than others. For example, the test
     22  suites for the core toolchain packages&mdash;GCC, Binutils,
     23  and Glibc&mdash;are of the utmost
    1724  importance due to their central role in a properly functioning system.
    1825  The test suites for GCC and Glibc can take a very long time to complete,
Note: See TracChangeset for help on using the changeset viewer.