| <?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="_NrbRUKeqEdmKDbQuyzCoqQ" |
| name="implement_tests,_0jO98MlgEdmt3adZL5Dmdw" guid="_NrbRUKeqEdmKDbQuyzCoqQ" |
| changeDate="2007-12-06T14:24:11.609-0800" version="1.0.0"> |
| <sections xmi:id="_A56NkKRKEdyLP-jEVj8Kyw" name="Select Test Cases to implement" |
| guid="_A56NkKRKEdyLP-jEVj8Kyw"> |
| <sectionDescription><p>
 |
| Select a set of Test Cases to develop into detailed, executable Test Scripts.&nbsp;
 |
| </p>
 |
| <p>
 |
| Work with project managers and developers to determine which Test Cases need detailed Test Scripts during the current
 |
| iteration. At a minimum, select Test Cases for requirements that are planned in the current or next iteration.
 |
| </p>
 |
| <p>
 |
| Perform each subsequent step in this task for each Test Script.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_WucQ4KRKEdyLP-jEVj8Kyw" name="Design the Test Script" guid="_WucQ4KRKEdyLP-jEVj8Kyw"> |
| <sectionDescription><p>
 |
| Sketch an outline of the Test Script as a logical sequence of steps. Review the data requirements of the Test Case, and
 |
| determine if existing data sets are sufficient, or if you need to develop new test data for this Test Script. Examine
 |
| system-wide requirements that apply to this Test Script, and note where they affect the expected results of a step.
 |
| </p>
 |
| <p>
 |
| If available, review a build that implements the scenario, or demonstrates similar functionality.
 |
| </p>Select an implementation technique for this design. At a minimum, determine if the Test Script will be manual or
 |
| automated. If the Test Case is well understood, it's best to implement an automated Test Script without first writing a
 |
| manual procedure. However, if the Test Case is new or novel, writing a manual Test Script can help validate the design of
 |
| the test and aid collaboration with other team members. See <a class="elementLinkWithType" href="./../../core.tech.common.extend_supp/guidances/guidelines/programming_automated_tests_7DA10019.html" guid="_0j5sUMlgEdmt3adZL5Dmdw">Guideline: Programming Automated Tests</a> for more details about this decision.</sectionDescription> |
| </sections> |
| <sections xmi:id="_VN5M0KuSEdmhFZtkg1nakg" name="Implement the executable Test Script" |
| guid="_VN5M0KuSEdmhFZtkg1nakg"> |
| <sectionDescription><p>
 |
| Develop a detailed, procedural Test Script based on your design. Use a request-response style that declares an exact
 |
| input, and expects an exact output.
 |
| </p>
 |
| <p>
 |
| Explain the pre-conditions that must be met before running this Test Script. Use temporary test data or put parameters
 |
| in your script for data values. Ensure that each post-condition in the Test Case is evaluated by steps in the Test
 |
| Script.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_WvBoYKuSEdmhFZtkg1nakg" name="Define specific test data" guid="_WvBoYKuSEdmhFZtkg1nakg"> |
| <sectionDescription><p>
 |
| Specify data values that are specific to the Test Script or reference existing test data. For example, instead of
 |
| specifying "a prime number", indicate an actual value such as "3."
 |
| </p>
 |
| <p>
 |
| If the Test Script uses a dataset (such as a file or database), add the new test data to it and parameterize the Test
 |
| Script to retrieve values from the dataset. Otherwise, add executable test data values to the steps of the Test Script.
 |
| This applies to both manual and automated scripts.
 |
| </p>
 |
| <p>
 |
| Identify and minimize dependencies between test data used or modified by other Test Scripts. Note dependencies in the
 |
| Test Script.
 |
| </p>
 |
| <p>
 |
| If necessary, create containers for your test data sets, and separate the production data from generated data.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_2IA70KRKEdyLP-jEVj8Kyw" name="Organize Test Scripts into suites" |
| guid="_2IA70KRKEdyLP-jEVj8Kyw"> |
| <sectionDescription><p>
 |
| Collect tests into related groups. The grouping you use depends on your test environment. Since the system under test
 |
| is undergoing its own evolution, create your test suites to facilitate regression testing, as well as system
 |
| configuration identification.
 |
| </p>
 |
| <p>
 |
| For help with test suite organization, see <a class="elementLinkWithType" href="./../../core.tech.common.extend_supp/guidances/guidelines/test_suite_D54EEBED.html" guid="_0aDz0MlgEdmt3adZL5Dmdw">Guideline: Test Suite</a>.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_X0dmcKuSEdmhFZtkg1nakg" name="Verify Test implementation" guid="_X0dmcKuSEdmhFZtkg1nakg"> |
| <sectionDescription><p>
 |
| Run the Test Script to verify that it implements the Test Case correctly. For manual testing, conduct a walkthrough of
 |
| the Test Script. For automated tests, verify that the Test Script executes correctly and produces the expected result.
 |
| </p>
 |
| <p>
 |
| Verify that the Test Script meets the criteria in <a class="elementLinkWithType" href="./../../core.tech.common.extend_supp/guidances/checklists/test_script_FBB4524E.html" guid="_0Z9tMMlgEdmt3adZL5Dmdw">Checklist: Test Script</a>.
 |
| </p>
 |
| <p>
 |
| Add or update the Test Script(s) in configuration management.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_ABwoIKRLEdyLP-jEVj8Kyw" name="Share and evaluate Test Scripts" |
| guid="_ABwoIKRLEdyLP-jEVj8Kyw"> |
| <sectionDescription><p>
 |
| Walk through the new or refined Test Scripts with the developers responsible for the related
 |
| scenarios.&nbsp;Optionally, the&nbsp;analysts and the stakeholders&nbsp;also participate.
 |
| </p>
 |
| <p>
 |
| Seek agreement that the Test Scripts correctly evaluate the expected results of the test, and that you understand the
 |
| implementation of the requirements. If the scenario is already implemented (such as in a developer workspace), walk
 |
| through a representative set of the Test Scripts using an implementation of the system.
 |
| </p></sectionDescription> |
| </sections> |
| <purpose><p>
 |
| To implement step-by-step Test Scripts that demonstrate the solution satisfies the requirements.
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
