| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription 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="_W6rc0Lv7EdmmUvZAZjqE3g" |
| name="run_developer_tests,_0iYCUMlgEdmt3adZL5Dmdw" guid="_W6rc0Lv7EdmmUvZAZjqE3g" |
| changeDate="2006-09-29T09:31:32.200-0700" version="1.0.0"> |
| <sections xmi:id="_MSnQsMP4EdmWKcx6ixEiwg" name="Run Developer Tests" guid="_MSnQsMP4EdmWKcx6ixEiwg"> |
| <sectionDescription><p>
 |
| Run the <a class="elementLink" href="./../../openup/workproducts/developer_test_8470ED13.html" guid="_0YuXEclgEdmt3adZL5Dmdw">Developer Test</a>s. The procedure will vary, depending on whether the test is manual or
 |
| automated and whether additional test components are necessary,&nbsp;such as&nbsp;drivers or stubs.
 |
| </p>
 |
| <p>
 |
| To run the tests, you need to make sure that you have initialized the test environment with all necessary elements,
 |
| such as software, hardware, tools, data, and so on.
 |
| </p>
 |
| <p>
 |
| Automated tests will often update a <a class="elementLink" href="./../../openup/workproducts/test_log_CBA2FDF4.html" guid="_0ZlSsMlgEdmt3adZL5Dmdw">Test Log</a>&nbsp;which you can evaluate to determine where your tests went wrong.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_NkRF0MP4EdmWKcx6ixEiwg" name="Evaluate test execution" guid="_NkRF0MP4EdmWKcx6ixEiwg"> |
| <sectionDescription><p>
 |
| Evaluate the test execution by analyzing the test run.&nbsp;
 |
| </p>
 |
| <p>
 |
| Testing will&nbsp;complete either&nbsp;normally or abnormally.&nbsp; For correctly implemented tests, a normal
 |
| completion represents a passed test, though it could warrant additional examination of the test log to ensure&nbsp;the
 |
| test&nbsp;ran as expected.&nbsp; Abnormal termination could be premature termination or just a test that does not
 |
| complete as intended.
 |
| </p>
 |
| <p>
 |
| Review the test log to understand any reported failures, warnings, or unexpected results. The cause of the problem(s)
 |
| might be that the implementation element being tested is faulty, a problem with the developer tests, or a problem with
 |
| the environment.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_SXPFkMP4EdmWKcx6ixEiwg" name="Respond to test results" guid="_SXPFkMP4EdmWKcx6ixEiwg"> |
| <sectionDescription><p>
 |
| Determine the appropriate corrective action to recover from a "failed" developer test run. If the implementation
 |
| element under test is faulty, fix the problem if possible and rerun the tests. If the problem is serious and cannot be
 |
| immediately addressed, perform the task <a class="elementLink" href="./../../openup/tasks/request_change_A048C387.html" guid="_0mwzEclgEdmt3adZL5Dmdw">Request Change</a> to report the defect. If the developer test is faulty fix the test and rerun the tests. If there was a
 |
| problem with the environment, resolve it and then rerun&nbsp;the tests.
 |
| </p>
 |
| <p>
 |
| When the developer tests pass, communicate the results. If the passing of these tests represent completion of a
 |
| requirement, this could involve updating the status of something on the <a class="elementLink" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>.
 |
| </p></sectionDescription> |
| </sections> |
| <keyConsiderations><p>
 |
| It is common to require that code pass all Developer tests before it can be delivered in an integrated build (see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/promoting_changes_9087B764.html" guid="_SM4YIL6dEdqti4GwqTkbsQ">Guideline: Promoting Changes</a>).
 |
| </p>
 |
| <p>
 |
| Pair with the Tester during all steps of this task to gain insight on testing and quality considerations.
 |
| </p></keyConsiderations> |
| <purpose>To verify that the implementation works as specified.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
