2
0
mirror of https://github.com/boostorg/website.git synced 2026-01-19 04:42:17 +00:00
Files
website/development/testing.html
2024-09-01 08:56:16 -07:00

243 lines
9.2 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>Testing</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="icon" href="/favicon.ico" type="image/ico" />
<link rel="stylesheet" type="text/css" href=
"../style-v2/section-development.css" />
<!--[if IE 7]> <style type="text/css"> body { behavior: url(/style-v2/csshover3.htc); } </style>
<![endif]-->
<style type="text/css">
/*<![CDATA[*/
th.c1 {font-style: italic}
/*]]>*/
</style>
<script defer data-domain="original.boost.org" src="https://plausible.io/js/script.js"></script></head><!--
Note: Editing website content is documented at:
https://www.boost.org/development/website_updating.html
-->
<body>
<div id="heading">
<!--#include virtual="/common/heading.html" -->
</div>
<div id="body">
<div id="body-inner">
<div id="content">
<div class="section" id="intro">
<div class="section-0">
<div class="section-title">
<h1>Testing</h1>
</div>
<div class="section-body" style="width: 796; height: 1802">
<ul class="toc">
<li><a href="#RegressionTesting">Regression Tests</a></li>
<li><a href="#Snapshots">Snapshots</a></li>
<li><a href="#Inspection">Inspection Reports</a></li>
<li><a href="#Introduction">More about regression
tests</a></li>
</ul>
<h2><a name="RegressionTesting" id=
"RegressionTesting"></a>Regression Tests</h2>
<p>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:</p>
<table summary="Regression Results">
<tr>
<th>Version</th>
<th colspan="2">Developers</th>
</tr>
<tr>
<td>Develop branch</td>
<td><a href=
"tests/develop/developer/summary.html">Summary</a></td>
<td><a href="tests/develop/developer/issues.html">Unresolved
Issues</a></td>
</tr>
<tr>
<td>Master branch</td>
<td><a href=
"tests/master/developer/summary.html">Summary</a></td>
<td><a href=
"tests/master/developer/issues.html">Unresolved
Issues</a></td>
</tr>
<!--
We used to generate pages for releases, haven't done that
for some time, but 1.35 results are still at:
https://www.boost.org/development/tests/release-1_35_0/user/summary_release.html
https://www.boost.org/development/tests/release-1_35_0/developer/summary.html
https://www.boost.org/development/tests/release-1_35_0/developer/issues.html
-->
</table>
<h2><a name="Snapshots" id="Snapshots"></a>Snapshots</h2>
<p>Snapshots are used for quality control checks.&nbsp; The
Unix tarballs and Windows zipballs are identical except for the
line endings exported from Git.</p>
<p>Because the snapshots represent work-in-process, they may
not be suitable for production use.</p>
<table summary="Snapshots">
<tr>
<th>Version</th>
<th>Download</th>
<th>Documentation</th>
</tr>
<tr>
<td>Master branch</td>
<td><a title="Boost master branch snapshots on sourceforge"
href=
"https://sourceforge.net/projects/boost/files/boost/snapshots/master/">
Sourceforge</a>, <a title=
"Boost master branch snapshots on archives.boost.io" href=
"https://archives.boost.io/master/">archives.boost.io</a>.</td>
<td><a title="Boost master branch documentation snapshot"
href="/doc/libs/master/">Documentation</a></td>
</tr>
<tr>
<td>Develop branch</td>
<td><a title=
"Boost develop branch snapshots on sourceforge" href=
"https://sourceforge.net/projects/boost/files/boost/snapshots/develop/">
Sourceforge</a>, <a title=
"Boost develop branch snapshots on archives.boost.io" href=
"https://archives.boost.io/develop">archives.boost.io</a>.</td>
<td><a title="Boost develop branch documentation snapshot"
href="/doc/libs/develop/">Documentation</a></td>
</tr>
</table>
<p>The Git master branch can be checked out from <a href=
"https://github.com/boostorg/boost">https://github.com/boostorg/boost</a>.</p>
<h2><a name="Inspection" id="Inspection"></a>Inspection
Reports</h2>
<p>The Boost snapshots are inspected daily to detect problems
such as missing copyrights or licenses. The Boost Inspection
Report tells all!</p>
<table summary="Regression Results">
<tr>
<th>Version</th>
</tr>
<tr>
<td><a href=
"http://boost.cowic.de/rc/docs-inspect-develop.html">Develop
branch</a></td>
</tr>
<tr>
<td><a href=
"http://boost.cowic.de/rc/docs-inspect-master.html">Master
branch</a></td>
</tr>
</table>
<h2><a name="Introduction" id="Introduction"></a>More about
regression tests</h2>
<p>Will all Boost libraries work with your compiler?&nbsp;
Unfortunately, the answer is "it depends". See the <a href=
"#RegressionTesting">regression testing results</a> to see
exactly what works and what doesn't.</p>
<p>Boost libraries rely on modern C++ features such as
templates and the C++ Standard Library.&nbsp; 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.</p>
<p>Boost library authors often expend a great deal of effort
trying to work around compiler deficiencies.&nbsp;
Nevertheless, some libraries will not compile at all with
certain compilers or may have crippled functionality.&nbsp;
Even if the current release of a compiler supports a boost
library, older versions of the compiler may not work
properly.</p>
<p>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.</p>
<h3>Warnings:</h3>
<ul>
<li>These tables are not a good indication of a particular
compiler's compliance with the C++ Standard.&nbsp; The Boost
libraries often contain workarounds which mask compiler
deficiencies.</li>
<li>Some regression tests are run only occasionally, and so
are relatively out-of-date.&nbsp; Check the date and revision
in the column heading.</li>
</ul>
<p>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.</p>
<p>A list of some of the organizations helping with testing is
listed on the <a href=
"/community/acknowledgements.html#testing">Acknowledgements
page</a>.</p>
</div>
</div>
</div>
</div>
<div id="sidebar">
<!--#include virtual="/common/sidebar-common.html" -->
<!--#include virtual="/common/sidebar-development.html" -->
</div>
<div class="clear"></div>
</div>
</div>
<div id="footer">
<div id="footer-left">
<div id="revised">
<p>Revised $Date$</p>
</div>
<div id="copyright">
<p>Copyright Rene Rivera 2007.</p>
</div><!--#include virtual="/common/footer-license.html" -->
</div>
<div id="footer-right">
<!--#include virtual="/common/footer-banners.html" -->
</div>
<div class="clear"></div>
</div>
</body>
</html>