abouttestsuites.xml 1.1 KB

12345678910111213141516171819202122232425
  1. <sect1 id="ch02-abouttestsuites">
  2. <title>About the test suites</title>
  3. <?dbhtml filename="abouttestsuites.html" dir="chapter02"?>
  4. <para>Most packages provide a test suite. Running the test suite for a newly
  5. built package is generally a good idea as it can provide a nice sanity check
  6. that everything compiled correctly. A test suite that passes its set of
  7. checks usually proves that the package is functioning mostly as the developer
  8. intended. It does not, however, guarantee that the package is totally bug
  9. free.</para>
  10. <para>Some test suites are more important than others. For example, the test
  11. suites for the core toolchain packages -- GCC, Binutils, and Glibc (the C
  12. library) -- are of the utmost importance due to their central positioning in a
  13. properly functioning system. But be warned, the test suites for GCC and Glibc
  14. can take a very long period of time to complete, especially on slower
  15. hardware.</para>
  16. <para>As you progress through the book and encounter the build commands to
  17. run the various test suites, we'll guide you on the relative importance of
  18. the test suite in question so that you can decide for yourself whether to
  19. run it or not.</para>
  20. </sect1>