|
Last change
on this file since e642efb3 was bea9517, checked in by Jim Gifford <clfs@…>, 19 years ago |
r1023@server (orig r1021): chris | 2006-01-08 00:36:31 -0800
Rewrote description of build process and test suite info, and added mention of test suites to some packages.
|
-
Property mode
set to
100644
|
|
File size:
995 bytes
|
| Line | |
|---|
| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
|---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
|---|
| 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 5 | %general-entities;
|
|---|
| 6 | ]>
|
|---|
| 7 |
|
|---|
| 8 | <sect1 id="ch-final-preps-abouttestsuites">
|
|---|
| 9 | <?dbhtml filename="abouttestsuites.html"?>
|
|---|
| 10 |
|
|---|
| 11 | <title>About the Test Suites</title>
|
|---|
| 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>
|
|---|
| 21 |
|
|---|
| 22 | </sect1>
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
