Google Git
Sign in
eclipse / epf / org.eclipse.epf.nl-libraries / 853e429f43a7d8294e63dacdec9cda1873f80c63 / . / OpenUP / OpenUP_SP / library / openup_basic / tasks / create_test_cases.xmi
blob: 59c2631ec21ba87e43848f65bbd021e912fdcea6 [file] [log] [blame]
<?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.3/uma.ecore" epf:version="1.0.0" xmi:id="_NrVKsKeqEdmKDbQuyzCoqQ" name="create_test_cases,_0iwc0clgEdmt3adZL5Dmdw" guid="_NrVKsKeqEdmKDbQuyzCoqQ" changeDate="2007-02-07T15:38:57.234-0800" version="1.0.0">
<sections xmi:id="_IJFSsKuSEdmhFZtkg1nakg" name="Review the requirements to be tested" guid="_IJFSsKuSEdmhFZtkg1nakg">
<sectionDescription>&lt;p&gt;
Work with&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/roles/analyst,_0VxJsMlgEdmt3adZL5Dmdw.html&quot;
guid=&quot;_0VxJsMlgEdmt3adZL5Dmdw&quot;&gt;Role: Analyst&lt;/a&gt; and &lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/roles/developer,_0YDosMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0YDosMlgEdmt3adZL5Dmdw&quot;&gt;Role:
Developer&lt;/a&gt;&amp;nbsp;to identify which use-case scenarios need new or additional test cases. Review the &lt;a
class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/iteration_plan,_0aQBEslgEdmt3adZL5Dmdw.html&quot;
guid=&quot;_0aQBEslgEdmt3adZL5Dmdw&quot;&gt;Artifact: Iteration Plan&lt;/a&gt;&amp;nbsp;to ensure you understand the scope of development for
the current iteration.&lt;br /&gt;
&lt;/p&gt;</sectionDescription>
</sections>
<sections xmi:id="_aDe_ILGcEdubqf8m_Zrvvg" name="Identify relevant Test Cases" guid="_aDe_ILGcEdubqf8m_Zrvvg">
<sectionDescription>&lt;p&gt;
Identify paths through the use-case scenario as unique test conditions.&amp;nbsp; Consider alternative or exception paths
from both a positive and negative perspective.&amp;nbsp;&amp;nbsp;Review the test ideas list for patterns of test cases that
apply to the use-case scenario.
&lt;/p&gt;
&lt;p&gt;
Discuss the requirement with the &lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html&quot; guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;&gt;Role:
Stakeholder&lt;/a&gt; to identify other conditions of satisfaction for the requirement.
&lt;/p&gt;
&lt;p&gt;
List the test cases with a unique name that identifies the condition they evaluate or their expected result.
&lt;/p&gt;</sectionDescription>
</sections>
<sections xmi:id="_LpbM8KuSEdmhFZtkg1nakg" name="Outline the Test Cases" guid="_LpbM8KuSEdmhFZtkg1nakg">
<sectionDescription>&lt;p&gt;
For each test case, write a brief description with an expected result.&amp;nbsp; Ensure that a casual reader can clearly
understand the difference between test cases.&amp;nbsp; Note the logical pre-conditions and post-conditions that apply to
each test case. Optionally, outline steps for the test case.
&lt;/p&gt;
&lt;p&gt;
Verify that test cases meet the &lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/guidances/checklists/test_case,_0Zxf8MlgEdmt3adZL5Dmdw.html&quot;
guid=&quot;_0Zxf8MlgEdmt3adZL5Dmdw&quot;&gt;Checklist: Test Case&lt;/a&gt;&amp;nbsp;guidelines.
&lt;/p&gt;
&lt;p&gt;
For more information on the test case, see &lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/guidances/templates/test_case,_0dT8IMlgEdmt3adZL5Dmdw.html&quot;
guid=&quot;_0dT8IMlgEdmt3adZL5Dmdw&quot;&gt;Template: Test Case&lt;/a&gt;.
&lt;/p&gt;</sectionDescription>
</sections>
<sections xmi:id="_NK18YKuSEdmhFZtkg1nakg" name="Identify test data needs" guid="_NK18YKuSEdmhFZtkg1nakg">
<sectionDescription>&lt;p&gt;
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.
&lt;/p&gt;
&lt;p&gt;
For more information on test data selection, see &lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/guidances/checklists/test_case,_0Zxf8MlgEdmt3adZL5Dmdw.html&quot;
guid=&quot;_0Zxf8MlgEdmt3adZL5Dmdw&quot;&gt;Checklist: Test Case&lt;/a&gt;.
&lt;/p&gt;</sectionDescription>
</sections>
<sections xmi:id="_Ok_mMKuSEdmhFZtkg1nakg" name="Share and evaluate the Test Cases" guid="_Ok_mMKuSEdmhFZtkg1nakg">
<sectionDescription>&lt;p&gt;
Walk through the test cases with the&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/roles/analyst,_0VxJsMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0VxJsMlgEdmt3adZL5Dmdw&quot;&gt;Role:
Analyst&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/roles/developer,_0YDosMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0YDosMlgEdmt3adZL5Dmdw&quot;&gt;Role:
Developer&lt;/a&gt;&amp;nbsp;responsible for the related&amp;nbsp;use-case scenario.&amp;nbsp;&amp;nbsp;Ideally, the &lt;a
class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html&quot;
guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;&gt;Role: Stakeholder&lt;/a&gt;&amp;nbsp;also participates.
&lt;/p&gt;
&lt;p&gt;
Ask the participants to agree that if &lt;em&gt;these test cases pass&lt;/em&gt;, they will consider these requirements
implemented.&amp;nbsp; Elicit additional test ideas from the &lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/roles/analyst,_0VxJsMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0VxJsMlgEdmt3adZL5Dmdw&quot;&gt;Role: Analyst&lt;/a&gt;
and the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html&quot;
guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;&gt;Role: Stakeholder&lt;/a&gt; to ensure you understand the expected behavior of the use-case
scenario.
&lt;/p&gt;
&lt;p&gt;
During the walkthrough, ensure that:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html&quot;
guid=&quot;_0VGbUMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Use Case&lt;/a&gt;&amp;nbsp;and &lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html&quot;
guid=&quot;_BVh9cL-CEdqb7N6KIeDL8Q&quot;&gt;Artifact: Supporting Requirements&lt;/a&gt;&amp;nbsp;planned for the current iteration have
test cases.
&lt;/li&gt;
&lt;li&gt;
All the participants agree with the expected results of the test cases.
&lt;/li&gt;
&lt;li&gt;
There are no&amp;nbsp;&lt;em&gt;other&lt;/em&gt; conditions of satisfaction for the requirement being tested, which indicates
either a missing test case or a missing requirement.
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
Optionally, capture new patterns of test cases&amp;nbsp;in&amp;nbsp;the test ideas list (see &lt;a class=&quot;elementLinkWithType&quot;
href=&quot;./../../openup_basic/guidances/concepts/test_ideas_list,_0jnYcMlgEdmt3adZL5Dmdw.html&quot;
guid=&quot;_0jnYcMlgEdmt3adZL5Dmdw&quot;&gt;Concept: Test Ideas List&lt;/a&gt;).
&lt;/p&gt;</sectionDescription>
</sections>
<purpose>&lt;p&gt;
To achieve a shared understanding of the specific conditions that the solution must meet.
&lt;/p&gt;</purpose>
</org.eclipse.epf.uma:TaskDescription>