| <?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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-H6ob8eA7gz_mOsk8ulSFMQ" name=",_R7atwJfIEdyZkIR-s-Y8wQ" guid="-H6ob8eA7gz_mOsk8ulSFMQ" changeDate="2010-09-15T12:46:34.530-0700" version="7.2.0"> |
| <keyConsiderations><p>
 |
| It is common to require that code pass all developer tests before it can be delivered in an integrated source code
 |
| repository.
 |
| </p>
 |
| <p>
 |
| Pair with testing experts to gain insight on testing and quality considerations.
 |
| </p>
 |
| <p>
 |
| The&nbsp;[Project Work]&nbsp;is implicitly used in implementation tasks to manage which requirements or change requests
 |
| are being realized in the code.
 |
| </p></keyConsiderations> |
| <sections xmi:id="_gjLBUJfIEdyZkIR-s-Y8wQ" name="Run developer tests" guid="_gjLBUJfIEdyZkIR-s-Y8wQ"> |
| <sectionDescription><p>
 |
| Run the developer tests.&nbsp;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 test results&nbsp;which you can evaluate to determine where your tests went wrong.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_haRocJfIEdyZkIR-s-Y8wQ" name="Evaluate test execution" guid="_haRocJfIEdyZkIR-s-Y8wQ"> |
| <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 results 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&nbsp;element being tested is faulty, a problem with the developer tests, or a problem
 |
| with the environment.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_itj1QJfIEdyZkIR-s-Y8wQ" name="Respond to test results" guid="_itj1QJfIEdyZkIR-s-Y8wQ"> |
| <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, 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></sectionDescription> |
| </sections> |
| <sections xmi:id="_C0_fYFQAEd2ECfw27om6fw" name="Promote changes for integration test" guid="_C0_fYFQAEd2ECfw27om6fw"> |
| <sectionDescription><p>
 |
| When the developer tests pass and no further work is need to complete the change set, promote the changes for
 |
| integration test. If the passing of these tests represent completion of a requirement update the status of the work
 |
| item.
 |
| </p></sectionDescription> |
| </sections> |
| <purpose>To verify that the implementation works as specified.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
