<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-YYMUwBepQ28JU78LtraO3w" name="xp_customer_test,{DF0EDBC7-4AAD-438D-89AA-64ECFE2416F5}" guid="-YYMUwBepQ28JU78LtraO3w" changeDate="2006-11-10T09:27:13.845-0800" version="1.0.0">
  <keyConsiderations>As more and more customer tests are added to the system, there will be a need to organize them in some way. Typically, the
testers and programmers will build and maintain some kind of customer test framework. As is the case for the production
code, it is important to let the framework evolve with the needs of the application. It is very easy to go overboard when
building a test framework.</keyConsiderations>
  <purpose>&lt;a id=&quot;XE_xp_customer_test__artifact_definition&quot; name=&quot;XE_xp_customer_test__artifact_definition&quot;&gt;&lt;/a&gt;&lt;a id=&quot;Purpose&quot;
name=&quot;Purpose&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_xp_customer_test__purpose_of&quot; name=&quot;XE_xp_customer_test__purpose_of&quot;&gt;&lt;/a&gt; 
&lt;p&gt;
    The &lt;a class=&quot;PresentationName&quot; guid=&quot;{DF0EDBC7-4AAD-438D-89AA-64ECFE2416F5}&quot;&gt;XP Customer Test&lt;/a&gt; demonstrates the
    presence of the system features as defined by the customer. They are the unambiguous and detailed requirements of the
    system.
&lt;/p&gt;</purpose>
</org.eclipse.epf.uma:ArtifactDescription>