| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-9gUpkUYqONF3x8UWwAO_zw" |
| name="failure_analysis_rpt_creation,_0jhR0MlgEdmt3adZL5Dmdw" guid="-9gUpkUYqONF3x8UWwAO_zw" |
| changeDate="2007-05-17T10:00:23.546-0700" version="1.0.0"> |
| <mainDescription><h3>
 |
| Introduction
 |
| </h3>
 |
| <p>
 |
| During testing, you will encounter failures related to the execution of your tests in different forms, such as code
 |
| defects, user errors, program malfunctions, and test scripting issues. This&nbsp;concept discusses some ways to conduct
 |
| failure analysis and then to report your findings.
 |
| </p>
 |
| <h3>
 |
| Failure Analysis
 |
| </h3>
 |
| <p>
 |
| After you run the tests, its good practice to identify inputs for review of the results of the testing effort. Some
 |
| likely sources are defects that occurred during the execution of test scripts, change request metrics, and&nbsp;<a class="elementLinkWithType" href="./../../../openup/workproducts/test_log_CBA2FDF4.html" guid="_0ZlSsMlgEdmt3adZL5Dmdw">Artifact: Test Log</a> details.
 |
| </p>
 |
| <p>
 |
| Running test scripts results in errors of different kinds such as uncovered defects, unexpected behavior, or general
 |
| failure of the test script to run properly. When you run test scripts, one of the most important things to do is to
 |
| distinguish between the causes and effects of failure. It is important to differentiate failures in the system under
 |
| test&nbsp;from those related to the tests themselves.
 |
| </p>
 |
| <p>
 |
| Change request metrics are useful in analyzing and correcting failures in the testing. Select metrics that will
 |
| facilitate creation of incident reports from a collection of change requests.
 |
| </p>
 |
| <p>
 |
| Change request metrics that you may find useful in your failure analysis include:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| test coverage
 |
| </li>
 |
| <li>
 |
| priority
 |
| </li>
 |
| <li>
 |
| impact
 |
| </li>
 |
| <li>
 |
| defect trends
 |
| </li>
 |
| <li>
 |
| density
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Finally, one of the most critical sources of your failure analysis is the&nbsp;<a class="elementLinkWithType" href="./../../../openup/workproducts/test_log_CBA2FDF4.html" guid="_0ZlSsMlgEdmt3adZL5Dmdw">Artifact: Test Log</a>.
 |
| Relevant logs might come from many sources: they might be captured by the tools you use (both test execution and
 |
| diagnostic tools), generated by automated tests or metrics tools, output from the target test items themselves, or
 |
| recorded manually by the tester. Gather all of the available test log sources and examine their content. Check that all
 |
| the scheduled testing executed to completion, and that all the needed tests&nbsp;have been scheduled.
 |
| </p>
 |
| <h3>
 |
| Self-Documenting Tests
 |
| </h3>
 |
| <p>
 |
| For automated tests, its important for the&nbsp;test itself to examine the results and clearly report itself as passing
 |
| or failing. This provides the most efficient way to run a suite of tests without the need for human intervention. When
 |
| authoring self-documenting tests, ensure that the reporting considers both passing and failing results.
 |
| </p>
 |
| <h3>
 |
| Recording Your Findings
 |
| </h3>
 |
| <p>
 |
| Once you have conducted your failure analysis, you might decide to formalize the results of this analysis by recording
 |
| your findings in a report. There are several factors that go into deciding whether to record your failure analysis in a
 |
| report. Some of the key factors include: level of testing formality, complexity of the testing effort, and the need to
 |
| communicate the testing results to the entire development team. In less formal environments, it may be sufficient to
 |
| record your failure analysis in&nbsp;a summary fashion.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
