<?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.5/uma.ecore"
    xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-WLBHLWZFnj682R-zwxcmvA"
    name="new_supporting_material,_MqFOsEaBEdy1HvT2z9d1Kg" guid="-WLBHLWZFnj682R-zwxcmvA"
    authors="John D. McGregor" changeDate="2007-10-04T21:21:09.453-0400" version="0.20">
  <mainDescription>&lt;p>&#xD;
    Testing in a software product line faces some technical and some organizational challenges in addition to those faced&#xD;
    when testing a traditionally developed product. In particular:&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    1. The testing process must manage a wider range of variability than testing a single product.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    2. The test infrastructure should&amp;nbsp;support a wider range of binding times for test values.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    3. The test artifacts&amp;nbsp;must be&amp;nbsp;reusable across a larger set of products than is typical in one-off&#xD;
    development.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    4.&amp;nbsp;Traditional testing is spread over several levels of aggregation, such as unit, integration, and system, and&#xD;
    over several teams charged with creating these different aggegations. Product line testing must also address&#xD;
    coordination between core asset and product development teams.&#xD;
&lt;/p>&lt;br />&#xD;
&lt;p>&#xD;
    Testing is a category of software development activities. Activities from this category appear at various points in the&#xD;
    development process. These activities are related and ordered in that each testing activity occurs at a specific point&#xD;
    in the development process and builds on the previous testing activities. It also has a relationship to the other&#xD;
    development activities that have occurred since the last testing activity. The figure below puts a set of testing&#xD;
    activities into context with other development activities.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    This set of web pages provides an overview of testing activities for a software product line. The activities are&#xD;
    basically the same as in a non-product line method but the emphasis shifts more toward the front end of the development&#xD;
    process. The emphasis also moves to a more general level, in the core assets, as well as addressing the usual level of&#xD;
    specificity at the product level.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;img style=&quot;WIDTH: 794px; HEIGHT: 600px&quot; height=&quot;600&quot; alt=&quot;&quot; src=&quot;./resources/testingPic.png&quot; width=&quot;600&quot; />&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The figure shows that testing starts at the earliest stages of development with a specific approach to inspection for&#xD;
    non-code assets and then incudes the traditional testing phases of unit, integration, and system testing.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
