| <?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_NqYIcqeqEdmKDbQuyzCoqQ" name="test_script,_0ZfMEMlgEdmt3adZL5Dmdw" guid="_NqYIcqeqEdmKDbQuyzCoqQ" changeDate="2008-08-15T00:55:57.000-0700" version="7.2.0"> |
| <purpose><p>
 |
| Test scripts implement a subset of required tests in an efficient and effective manner.
 |
| </p></purpose> |
| <impactOfNotHaving>Without this artifact, it is difficult to ensure that tests are run consistently so that results are repeatable and errors
 |
| can be recreated. If you do not use a test script, it is more difficult to verify that errors were not caused because of
 |
| the way tests were run.</impactOfNotHaving> |
| <reasonsForNotNeeding><p>
 |
| This artifact might not be required if the tests are simple or if testing is done on an informal basis. However, for
 |
| this approach to be successful, testers must track their processes, as they might need to recreate a problem scenario.
 |
| Alternatively, you can use automatic capture and playback tools to provide a record of testing.
 |
| </p></reasonsForNotNeeding> |
| </org.eclipse.epf.uma:ArtifactDescription> |
