Files
website2022/development/testing.html
Frank Wiles dde98de1fb Initial Content Conversion
This is based off of revision 56094d2c9f510f5ee4f1ffd4eb6b73788aaa62d7
of https://github.com/boostorg/website/.

URL of exact commit is: 56094d2c9f
2022-08-14 11:21:12 -05:00

145 lines
4.1 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: Testing
copyright: Rene Rivera 2007.
revised:
---
Testing
/\*<![CDATA[\*/
th.c1 {font-style: italic}
/\*]]>\*/
Testing
=======
* [Regression Tests](#RegressionTesting)
* [Snapshots](#Snapshots)
* [Inspection Reports](#Inspection)
* [More about regression
tests](#Introduction)
Regression Tests
----------------
A group of volunteers donate CPU cycles and large amounts of
disk space to collectively produce the regression testing
result tables. Various Boost repository versions are tested for
the benefit of library developers and interested users:
| Version | Developers |
| --- | --- |
| Develop branch | [Summary](tests/develop/developer/summary.html) | [Unresolved
Issues](tests/develop/developer/issues.html) |
| Master branch | [Summary](tests/master/developer/summary.html) | [Unresolved
Issues](tests/master/developer/issues.html) |
Snapshots
---------
Snapshots are used for quality control checks.  The
Unix tarballs and Windows zipballs are identical except for the
line endings exported from Git.
Because the snapshots represent work-in-process, they may
not be suitable for production use.
| Version | Download | Documentation |
| --- | --- | --- |
| Master branch | [Sourceforge](https://sourceforge.net/projects/boost/files/boost/snapshots/master/ "Boost master branch snapshots on sourceforge"), [JFrog.io](https://boostorg.jfrog.io/artifactory/main/master/ "Boost master branch snapshots on JFrog.io"). | [Documentation](/doc/libs/master/ "Boost master branch documentation snapshot") |
| Develop branch | [Sourceforge](https://sourceforge.net/projects/boost/files/boost/snapshots/develop/ "Boost develop branch snapshots on sourceforge"), [JFrog.io](https://boostorg.jfrog.io/artifactory/main/develop "Boost develop branch snapshots on JFrog.io"). | [Documentation](/doc/libs/develop/ "Boost develop branch documentation snapshot") |
The Git master branch can be checked out from <https://github.com/boostorg/boost>.
Inspection
Reports
-------------------
The Boost snapshots are inspected daily to detect problems
such as missing copyrights or licenses. The Boost Inspection
Report tells all!
| Version |
| --- |
| [Develop
branch](http://boost.cowic.de/rc/docs-inspect-develop.html) |
| [Master
branch](http://boost.cowic.de/rc/docs-inspect-master.html) |
More about
regression tests
----------------------------
Will all Boost libraries work with your compiler? 
Unfortunately, the answer is "it depends". See the [regression testing results](#RegressionTesting) to see
exactly what works and what doesn't.
Boost libraries rely on modern C++ features such as
templates and the C++ Standard Library.  Most modern
compilers support those major features fairly well. But even
today, years after the adoption of the C++ Standard, some
compilers still don't support important minor features like
partial template specialization.
Boost library authors often expend a great deal of effort
trying to work around compiler deficiencies. 
Nevertheless, some libraries will not compile at all with
certain compilers or may have crippled functionality. 
Even if the current release of a compiler supports a boost
library, older versions of the compiler may not work
properly.
Boost releases are run through regression tests which
automatically generates compiler status tables for various
platforms. Unless otherwise indicated, the C++ Standard Library
implementation is the one shipped with the compiler.
### Warnings:
* These tables are not a good indication of a particular
compiler's compliance with the C++ Standard.  The Boost
libraries often contain workarounds which mask compiler
deficiencies.
* Some regression tests are run only occasionally, and so
are relatively out-of-date.  Check the date and revision
in the column heading.
The development code is being updated several times a day,
so it may contain bug fixes, compiler workarounds, new
features, and even whole new libraries. It may be unstable,
however.
A list of some of the organizations helping with testing is
listed on the [Acknowledgements
page](/community/acknowledgements.html#testing).