- Timestamp:
- 05/17/14 21:50:17 (10 years ago)
- Branches:
- clfs-3.0.0-sysvinit, sysvinit
- Children:
- e8f3474
- Parents:
- dbf50c0c
- Location:
- BOOK
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/final-preps/abouttestsuites.xml
rdbf50c0c r5f63ccf 11 11 <title>About the Test Suites</title> 12 12 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> 21 19 22 20 </sect1> -
BOOK/final-system/common/testsuitesagain.xml
rdbf50c0c r5f63ccf 12 12 13 13 <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—GCC, Binutils, and Glibc—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—GCC, Binutils, 23 and Glibc—are of the utmost 17 24 importance due to their central role in a properly functioning system. 18 25 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.