<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-K2LlBQ2XcLYLNSj6V_fKWw" name="new_supporting_material,_SCRugEkKEdyeY4JQKtaxKg" guid="-K2LlBQ2XcLYLNSj6V_fKWw" changeDate="2009-09-07T04:30:44.000-0400">
  <mainDescription>&lt;p>
    The goal for the testing practice is to&amp;nbsp;contribute to&amp;nbsp;the delivery of defect-free software while consuming
    the minimal amount of resources.
&lt;/p>
&lt;p>
    The main strategy for achieving this goal is to minimize&amp;nbsp;the &lt;a class=&quot;elementLink&quot;
    href=&quot;./../../../ProductLineTestingMethod/guidances/concepts/defect_live_range_534C1830.html&quot;
    guid=&quot;_Oq7aMFBHEdySQol4--Araw&quot;>Defect live range&lt;/a> for defects in the core assets and product-specific assets. The
    tactics to be used in this&amp;nbsp;strategy include design tactics, that are described elsewhere, and testing tactics. The
    testing tactics&amp;nbsp;include a test practice that defines a test activity for each development activity. The assumption
    is that more and earlier testing activities will find defects earlier than in a traditional process.
&lt;/p>
&lt;p>
    &lt;br />
    A secondary strategy is to achieve &lt;a class=&quot;elementLink&quot;
    href=&quot;./../../../ProductLineTestingMethod/guidances/concepts/strategic_reuse_C14D2B56.html&quot;
    guid=&quot;_NGaq8IPCEdy-WICub0uKhw&quot;>Strategic reuse&lt;/a>. Associated tactics include the explicit design of a test
    infrastructure accounting for the variation architecture of the product line and an explicit design of the test data to
    identify opportunities for reuse.
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
