| <?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-14T11:16:29.008-0400" |
| version="7.2.0"> |
| <mainDescription>This artifact&nbsp;provides a detailed, typically time-based record that serves both as verification that a set of tests
 |
| were executed, and provides information relating to the success of those tests.&nbsp; The focus is typically on the
 |
| provision of an accurate audit trail, enabling post-execution diagnosis of failures to be undertaken.&nbsp; This raw data
 |
| will subsequently be analyzed to help determine the results of some aspect of the test effort.</mainDescription> |
| <purpose><ul>
 |
| <li>
 |
| To provide verification that a set of tests was executed
 |
| </li>
 |
| <li>
 |
| To provide information relating to the success of those tests
 |
| </li>
 |
| </ul></purpose> |
| <impactOfNotHaving><p>
 |
| Without this or similar documentation, there is no record of which tests were executed successfully, what variances
 |
| were discovered, and what action was taken. If this information is not available:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| There will be no way to know which tests passed and which failed
 |
| </li>
 |
| <li>
 |
| There will be no way to assess the status of testing and the quality of the product at that level of testing
 |
| </li>
 |
| <li>
 |
| It will be difficult to know how many tests remain outstanding
 |
| </li>
 |
| <li>
 |
| Contractual and legal issues may arise
 |
| </li>
 |
| </ul></impactOfNotHaving> |
| <reasonsForNotNeeding><p>
 |
| <font size="2">There is no reason not to log the results of testing, since, without them, testing has little value. The
 |
| only situation where this may not be formally done is when ad hoc testing is conducted. In this case also, any problems
 |
| that are found will be recorded along with resolution.</font>
 |
| </p></reasonsForNotNeeding> |
| <representationOptions><p>
 |
| Since this is a collection of raw data for subsequent analysis, it can be represented in a number of ways.&nbsp; Some
 |
| suggestions are:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| For manual tests, 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> |
