| <?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.4/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.2.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.2.0" xmi:id="_NrVKsKeqEdmKDbQuyzCoqQ" |
| name="create_test_cases,_0iwc0clgEdmt3adZL5Dmdw" guid="_NrVKsKeqEdmKDbQuyzCoqQ" |
| changeDate="2007-02-07T15:38:57.234-0800" version="1.0.0"> |
| <keyConsiderations><p>
 |
| Develop test cases in parallel with requirements so that Analysts and Stakeholders 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> |
| <sections xmi:id="_IJFSsKuSEdmhFZtkg1nakg" name="Review the requirements to be tested" |
| guid="_IJFSsKuSEdmhFZtkg1nakg"> |
| <sectionDescription><p>
 |
| Work with analysts and developers&nbsp;to identify which scenarios and requirements&nbsp;need new or additional test
 |
| cases. Review the Plans&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;Review the test ideas list for patterns of test cases that apply to the
 |
| scenario.
 |
| </p>
 |
| <p>
 |
| Discuss the requirement with&nbsp;stakeholders 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.&nbsp; Ensure that a casual reader can clearly
 |
| understand the difference between test cases.&nbsp; 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="./../../core.tech.common.base/guidances/checklists/test_case_9D3F2E96.html"
 |
| guid="_0Zxf8MlgEdmt3adZL5Dmdw">Checklist: Test Case</a>&nbsp;guidelines.
 |
| </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="./../../core.tech.common.base/guidances/checklists/test_data_48E804D.html"
 |
| guid="_KZQJMBhBEduxCP6DVVLxsA">Checklist: Test Data</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 analysts and developers&nbsp;responsible for the related
 |
| scenario.&nbsp;&nbsp;Ideally, the stakeholders will&nbsp;also participate.
 |
| </p>
 |
| <p>
 |
| Ask the participants to agree that if <em>these test cases pass</em>, they will consider these requirements
 |
| implemented.&nbsp; Elicit additional test ideas from Analysts and Stakeholders to ensure you understand the expected
 |
| behavior of the scenario.
 |
| </p>
 |
| <p>
 |
| During the walkthrough, ensure that:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The requirements&nbsp;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&nbsp;<em>other</em> conditions of satisfaction for the requirement being tested, which indicates
 |
| either a missing test case or a missing requirement.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Optionally, capture new patterns of test cases&nbsp;in&nbsp;the test ideas list (see <a class="elementLinkWithType"
 |
| href="./../../core.tech.common.base/guidances/concepts/test_ideas_ED562B58.html"
 |
| guid="_0jnYcMlgEdmt3adZL5Dmdw">Concept: Test Ideas</a>).
 |
| </p></sectionDescription> |
| </sections> |
| <purpose><p>
 |
| To achieve a shared understanding of the specific conditions that the solution must meet.
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
