| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-dwfXb2dWJOQkTuLo-BTFeQ" |
| name="xp_unit_test,{D156652E-7C52-4EBD-8F23-F38169877A57}" guid="-dwfXb2dWJOQkTuLo-BTFeQ" |
| changeDate="2006-11-13T16:57:02.728-0500" version="1.0.0"> |
| <mainDescription><p>
 |
| <a class="PresentationName" guid="{D156652E-7C52-4EBD-8F23-F38169877A57}">XP Unit Test</a>s are usually implemented at
 |
| the class level (in OO languages) and test the public interface. For every class in the system, a test class exists.
 |
| Popular test frameworks are available usually for free (such as JUnit, CppUnit, CppUnitLite, NUnit). These are simple
 |
| tools that help the developer to organize and run unit tests. These tests drive the programmer development and tell the
 |
| programmer that the code works as the programmer expects.
 |
| </p></mainDescription> |
| <purpose><a id="XE_xp_unit_test__artifact_definition" name="XE_xp_unit_test__artifact_definition"></a><a id="Purpose" name="Purpose"></a><a id="XE_xp_unit_test__purpose_of" name="XE_xp_unit_test__purpose_of"></a> 
 |
| <p>
 |
| An <a class="PresentationName" guid="{D156652E-7C52-4EBD-8F23-F38169877A57}">XP Unit Test</a> is written by developers
 |
| to ensure that all system components work as expected. <a class="PresentationName" guid="{D156652E-7C52-4EBD-8F23-F38169877A57}">XP Unit Test</a> give the developers the confidence to modify the system
 |
| and feel confident that everything still works.
 |
| </p></purpose> |
| </org.eclipse.epf.uma:ArtifactDescription> |