| <?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="_NqePEKeqEdmKDbQuyzCoqQ" |
| name="test_log,_0ZlSsMlgEdmt3adZL5Dmdw" guid="_NqePEKeqEdmKDbQuyzCoqQ" changeDate="2008-08-15T12:57:11.671-0700" |
| version="7.2.0"> |
| <mainDescription>This
 |
| artifact provides a detailed, typically time-based record that both verifies
 |
| that a set of tests were run, and provides information that relates to the
 |
| success of those tests. The focus is typically on providing an accurate audit
 |
| trail, which enables you to undertake a post-run diagnosis of failures. This
 |
| raw data is subsequently analyzed to determine the results of an aspect of
 |
| the test effort.</mainDescription> |
| <purpose><ul>
 |
| <li> To provide verification that a set of tests was run </li>
 |
| <li> To provide information that relates to the success of those tests
 |
| </li>
 |
| </ul></purpose> |
| <impactOfNotHaving><p> 
 |
| Without this or similar documentation, there is no record of which tests
 |
| were run, what variances were discovered, and what action was taken. If this
 |
| information is not available: </p> <ul>
 |
| <li> There is no way to know which tests passed and which failed 
 |
| </li>
 |
| <li> There is no way to assess the status of testing and the quality
 |
| of the product at that level of testing </li>
 |
| <li> It is difficult to know how many tests remain outstanding 
 |
| </li>
 |
| <li> Contractual and legal issues might arise </li>
 |
| </ul></impactOfNotHaving> |
| <reasonsForNotNeeding><p
 |
| > When you execute automated tests, test logs are automatically produced.
 |
| Typically, the issue is not whether to produce the test log, but whether
 |
| to keep a record, and where to keep the records. For manual testing, the issue
 |
| is whether to keep a separate test log or to summarize the test results in
 |
| another form. </p></reasonsForNotNeeding> |
| <representationOptions><p
 |
| > Because this is a collection of raw data for subsequent analysis, it can
 |
| be represented in a number of ways: </p> <ul>
 |
| <li> For manual tests<?Pub Caret?>, log the actual results on a copy
 |
| of the manual Test Script </li>
 |
| <li> For automated tests, direct the output to log files that you
 |
| can trace back to the automated Test Script </li>
 |
| <li> Track raw results data in a test management tool </li>
 |
| </ul></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
