---
title: "Testing Guide for 4.10-RELEASE"
sidenav: download
---

++++


<h3>Goals</h3>

<p>As part of our on-going effort to improve the release engineering
  process, we have identified several areas that need significant
  quality assurance testing during the release candidate phase.
  Below, we've listed the changes in 4.10-RELEASE that we feel merit
  the most attention due to their involving substantial changes to the
  system, or having arrived late in the development cycle leading up
  to the release.  In general, our goal in the QA process is to
  attempt to check a number of things:</p>

<ul>
  <li>The system has not regressed with respects to stability, correctness,
    interoperability, or performance of features present in prior
    releases.<br clear="none" /><br clear="none" /></li>

  <li>New features result in the desired improvement in stability,
    correctness, interoperability, or performance.</li>
</ul>

<p>To effectively determine this, it's desirable to test the system in
  a diverse set of environments, applying a wide set of workloads,
  forcing the system to operate both within and outside its normal
  specification.  Particular focus should often be placed on the
  continuing (or new) capability of the system to perform correctly
  when used in concert with systems from other vendors.</p>

<h3>Features to explore carefully:</h3>

<ul>
  <li>There was a large merge of the USB code from RELENG_5 into RELENG_4.
    This requires as much testing as possible to make sure that no devices
    have regressed in stability or functionality.</li>
</ul>

<p>The <a href="../relnotes/" shape="rect">release notes</a> will always be
  a good place to look for things to test.</p>

<h3>Known Issues</h3>
<ul>
  <li>No known issues at this time.</li>
</ul>

</div>
          <br class="clearboth" />
        </div>
        
++++

