| <?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.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="_NqYIcqeqEdmKDbQuyzCoqQ" |
| name="test_script,_0ZfMEMlgEdmt3adZL5Dmdw" guid="_NqYIcqeqEdmKDbQuyzCoqQ" changeDate="2008-08-14T11:54:15.383-0400" |
| version="7.2.0"> |
| <purpose><p>
 |
| To provide the implementation of a subset of required tests in an efficient and effective manner.
 |
| </p></purpose> |
| <impactOfNotHaving>Without a this artifact it will be difficult to ensure that tests are being carried out in a consistent manner so that
 |
| results are repeatable and any errors discovered can be recreated.&nbsp; It also makes it more difficult to validate that
 |
| errors were not caused because of the way in which tests were executed.</impactOfNotHaving> |
| <reasonsForNotNeeding><p>
 |
| This artifact may not be required if&nbsp;the tests are very simple in nature or testing is only being done on an
 |
| informal basis.&nbsp; However, in order for this approach to be successful, testers need to be disciplined in tracking
 |
| their processes, as they may have to recreate a problem scenario.&nbsp; Alternatively, automatic capture/playback tools
 |
| could be put in place to provide a record of such testing.
 |
| </p></reasonsForNotNeeding> |
| </org.eclipse.epf.uma:ArtifactDescription> |
