<?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>&lt;p>&#xD;
    It is common to require that code pass all developer tests before it can be delivered in an integrated source code&#xD;
    repository.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Pair with testing experts to gain insight on testing and quality considerations.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The&amp;nbsp;[Project Work]&amp;nbsp;is implicitly used in implementation tasks to manage which requirements or change requests&#xD;
    are being realized in the code.&#xD;
&lt;/p></keyConsiderations>
  <sections xmi:id="_gjLBUJfIEdyZkIR-s-Y8wQ" name="Run developer tests" guid="_gjLBUJfIEdyZkIR-s-Y8wQ">
    <sectionDescription>&lt;p>&#xD;
    Run the developer tests.&amp;nbsp;The procedure will vary, depending on whether the test is manual or automated and whether&#xD;
    additional test components are necessary,&amp;nbsp;such as&amp;nbsp;drivers or stubs.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    To run the tests, you need to make sure that you have initialized the test environment with all necessary elements,&#xD;
    such as software, hardware, tools, data, and so on.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Automated tests will often update a test results&amp;nbsp;which you can evaluate to determine where your tests went wrong.&#xD;
&lt;/p></sectionDescription>
  </sections>
  <sections xmi:id="_haRocJfIEdyZkIR-s-Y8wQ" name="Evaluate test execution" guid="_haRocJfIEdyZkIR-s-Y8wQ">
    <sectionDescription>&lt;p>&#xD;
    Evaluate the test execution by analyzing the test run.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Testing will&amp;nbsp;complete either&amp;nbsp;normally or abnormally.&amp;nbsp; For correctly implemented tests, a normal&#xD;
    completion represents a passed test, though it could warrant additional examination of the test results log to&#xD;
    ensure&amp;nbsp;the test&amp;nbsp;ran as expected.&amp;nbsp; Abnormal termination could be premature termination or just a test&#xD;
    that does not complete as intended.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Review the test log to understand any reported failures, warnings, or unexpected results. The cause of the problem(s)&#xD;
    might be that the implementation&amp;nbsp;element being tested is faulty, a problem with the developer tests, or a problem&#xD;
    with the environment.&#xD;
&lt;/p></sectionDescription>
  </sections>
  <sections xmi:id="_itj1QJfIEdyZkIR-s-Y8wQ" name="Respond to test results" guid="_itj1QJfIEdyZkIR-s-Y8wQ">
    <sectionDescription>&lt;p>&#xD;
    Determine the appropriate corrective action to recover from a &quot;failed&quot; developer test run. If the implementation&#xD;
    element under test is faulty, fix the problem if possible and rerun the tests. If the problem is serious and cannot be&#xD;
    immediately addressed, report the defect. If the developer test is faulty fix the test and rerun the tests. If there&#xD;
    was a problem with the environment, resolve it and then rerun&amp;nbsp;the tests.&#xD;
&lt;/p></sectionDescription>
  </sections>
  <sections xmi:id="_C0_fYFQAEd2ECfw27om6fw" name="Promote changes for integration test" guid="_C0_fYFQAEd2ECfw27om6fw">
    <sectionDescription>&lt;p>&#xD;
    When the developer tests pass and no further work is need to complete the change set, promote the changes for&#xD;
    integration test. If the passing of these tests represent completion of a requirement update the status of the work&#xD;
    item.&#xD;
&lt;/p></sectionDescription>
  </sections>
  <purpose>To verify that the implementation works as specified.</purpose>
</org.eclipse.epf.uma:TaskDescription>
