| <?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="_NrVKsKeqEdmKDbQuyzCoqQ" |
| name="create_test_cases,_0iwc0clgEdmt3adZL5Dmdw" guid="_NrVKsKeqEdmKDbQuyzCoqQ" |
| changeDate="2007-06-05T14:36:55.703-0700" version="1.0.0"> |
| <sections xmi:id="_IJFSsKuSEdmhFZtkg1nakg" name="Review the requirements to be tested" |
| guid="_IJFSsKuSEdmhFZtkg1nakg"> |
| <sectionDescription><p>
 |
| 
 |
| Work with&nbsp;<a class="elementLink" href="./../../openup/roles/analyst_39D7C49B.html" guid="_0VxJsMlgEdmt3adZL5Dmdw">Analyst</a> and <a class="elementLink" href="./../../openup/roles/developer_C633AB7.html" guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a>&nbsp;to identify which scenarios need new or additional test cases. Review
 |
| 
 |
| the <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>&nbsp;to ensure you understand the scope of development for the
 |
| 
 |
| current iteration.<br />
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_aDe_ILGcEdubqf8m_Zrvvg" name="Identify relevant Test Cases" guid="_aDe_ILGcEdubqf8m_Zrvvg"> |
| <sectionDescription><p>
 |
| 
 |
| Identify paths through the scenario as unique test conditions.&nbsp;Consider alternative or exception paths from both a
 |
| 
 |
| positive and negative perspective.&nbsp;&nbsp;
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| Discuss the requirement with the <a class="elementLink" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a> to identify other conditions of satisfaction for the requirement.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| List the test cases with a unique name that identifies the condition they evaluate or their expected result.
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_LpbM8KuSEdmhFZtkg1nakg" name="Outline the Test Cases" guid="_LpbM8KuSEdmhFZtkg1nakg"> |
| <sectionDescription><p>
 |
| 
 |
| For each test case, write a brief description with an expected result. Ensure that a casual reader can clearly
 |
| 
 |
| understand the difference between test cases. Note the logical pre-conditions and post-conditions that apply to each
 |
| 
 |
| test case. Optionally, outline steps for the test case.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| Verify that test cases meet the <a class="elementLinkWithType" href="./../../openup/guidances/checklists/test_case_9D3F2E96.html" guid="_0Zxf8MlgEdmt3adZL5Dmdw">Checklist: Test Case</a> guidelines.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| For more information on the test case, see <a class="elementLinkWithType" href="./../../openup/guidances/templates/test_case_A18913A5.html" guid="_0dT8IMlgEdmt3adZL5Dmdw">Template: Test Case</a>.
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_NK18YKuSEdmhFZtkg1nakg" name="Identify test data needs" guid="_NK18YKuSEdmhFZtkg1nakg"> |
| <sectionDescription><p>
 |
| 
 |
| Review each test case and note where data input or output might be required. Identify the type, quantity, and
 |
| 
 |
| uniqueness of the required data, and add these observations to the test case. Focus on articulating the data needed and
 |
| 
 |
| not on creating specific data.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| For more information on test data selection, see <a class="elementLinkWithType" href="./../../openup/guidances/checklists/test_case_9D3F2E96.html" guid="_0Zxf8MlgEdmt3adZL5Dmdw">Checklist: Test Case</a>.
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_Ok_mMKuSEdmhFZtkg1nakg" name="Share and evaluate the Test Cases" |
| guid="_Ok_mMKuSEdmhFZtkg1nakg"> |
| <sectionDescription><p>
 |
| 
 |
| Walk through the test cases with the <a class="elementLink" href="./../../openup/roles/analyst_39D7C49B.html" guid="_0VxJsMlgEdmt3adZL5Dmdw">Analyst</a> and <a class="elementLink" href="./../../openup/roles/developer_C633AB7.html" guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a> responsible for the related scenario. Ideally, the <a class="elementLink" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a> also participates.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| Ask the participants to agree that if <em>these test cases pass</em>, they will consider these requirements
 |
| 
 |
| implemented. Elicit additional test ideas from the <a class="elementLinkWithType" href="./../../openup/roles/analyst_39D7C49B.html" guid="_0VxJsMlgEdmt3adZL5Dmdw">Role: Analyst</a> and the <a class="elementLink" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a>
 |
| 
 |
| to ensure you understand the expected behavior of the scenario.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| During the walkthrough, ensure that:
 |
| 
 |
| </p>
 |
| 
 |
| <ul>
 |
| 
 |
| <li>
 |
| 
 |
| The <a class="elementLink" href="./../../openup/workproducts/use_case_22BE66E2.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Use Case</a>s and <a class="elementLink" href="./../../openup/workproducts/supporting_requirements_spec_7D9DD47C.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Supporting Requirements Specification</a> planned for the current iteration have
 |
| 
 |
| test cases.
 |
| 
 |
| </li>
 |
| 
 |
| <li>
 |
| 
 |
| All the participants agree with the expected results of the test cases.
 |
| 
 |
| </li>
 |
| 
 |
| <li>
 |
| 
 |
| There are no <em>other</em> conditions of satisfaction for the requirement being tested, which indicates either a
 |
| 
 |
| missing test case or a missing requirement.
 |
| 
 |
| </li>
 |
| 
 |
| </ul></sectionDescription> |
| </sections> |
| <keyConsiderations><p>
 |
| Develop test cases in parallel with requirements so that <a class="elementLinkWithType" href="./../../openup/roles/analyst_39D7C49B.html" guid="_0VxJsMlgEdmt3adZL5Dmdw">Role: Analyst</a> and <a class="elementLinkWithType" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Role: Stakeholder</a> can agree with the specific conditions of satisfaction for each requirement. The test cases act as
 |
| acceptance criteria by expanding on the intent of the system&nbsp;through actual scenarios of use.&nbsp;This allows
 |
| team members to measure progress in terms of passing test cases.&nbsp;
 |
| </p></keyConsiderations> |
| <purpose><p>
 |
| 
 |
| 
 |
| To achieve a shared understanding of the specific conditions that the solution must meet.
 |
| 
 |
| 
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
