blob: f0a296dc55148868095fb7f1a1db531f0e3f6a85 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<!-- VERSION rmc:7.1.0 -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<!-- START NON-TRANSLATABLE -->
<title>\openup_basic\tasks\implement_tests.xmi</title>
</head>
<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
<body>
Element Name: implement_tests.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0jO98MlgEdmt3adZL5Dmdw CRC: 467065627 -->Implement Tests<!-- END:presentationName,_0jO98MlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_0jO98MlgEdmt3adZL5Dmdw CRC: 363878856 -->Implement one or more test artifacts to enable the validation of the software product through actually running the system. Combine tests to facilitate appropriate breadth and depth of test coverage.<!-- END:briefDescription,_0jO98MlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,_NrbRUKeqEdmKDbQuyzCoqQ CRC: 776360132 --><p>
To implement one or more tests that can be executed to validate a system.
</p><!-- END:purpose,_NrbRUKeqEdmKDbQuyzCoqQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_S8JzsKuSEdmhFZtkg1nakg CRC: 17534694 -->Select appropriate implementation technique<!-- END:name,_S8JzsKuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_S8JzsKuSEdmhFZtkg1nakg CRC: 3668959222 --><p>
Select one or several of the following test implementation&nbsp;techniques:
</p>
<ul>
<li>
manual test scripts
</li>
<li>
programmed test scripts
</li>
<li>
recorded test scripts
</li>
</ul><!-- END:sectionDescription,_S8JzsKuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_VN5M0KuSEdmhFZtkg1nakg CRC: 3796032468 -->Implement the test<!-- END:name,_VN5M0KuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_VN5M0KuSEdmhFZtkg1nakg CRC: 3485335602 --><p>
Using your test-ideas list and test cases as inputs, set up your specifications, spreadsheet, or&nbsp;automated
tool&nbsp;to record scripts needed to conduct the test.&nbsp;If you are recording explicit steps for your test,
navigate through the system under test identifying steps, groups of related steps, verification points, and control
points.
</p><!-- END:sectionDescription,_VN5M0KuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_WvBoYKuSEdmhFZtkg1nakg CRC: 1091386899 -->Establish external data sets<!-- END:name,_WvBoYKuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_WvBoYKuSEdmhFZtkg1nakg CRC: 2925873557 -->Create containers for your test data sets. Separate the production data from generated data. Associate your data sets with
a given build of the system under test.&nbsp;If data sets are associated with a particular part of the system under test,
mark them accordingly.<!-- END:sectionDescription,_WvBoYKuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_X0dmcKuSEdmhFZtkg1nakg CRC: 3804472598 -->Verify Test implementation<!-- END:name,_X0dmcKuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_X0dmcKuSEdmhFZtkg1nakg CRC: 3858350611 --><p>
Run the test script to verify that it implements the tests correctly. For manual testing,&nbsp;conduct a walkthrough of
the test script. For automated tests, verify that&nbsp;the test implementation will involve some degree of the
configuration of the testing tool.
</p><!-- END:sectionDescription,_X0dmcKuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_Y-ABYKuSEdmhFZtkg1nakg CRC: 2274590756 -->Organize tests into test suites<!-- END:name,_Y-ABYKuSEdmhFZtkg1nakg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_Y-ABYKuSEdmhFZtkg1nakg CRC: 2296266041 --><p>
Collect tests into related groups. The grouping you use depends on your test environment. For example, you can organize
test cases, test scripts, and test data hierarchically to facilitate navigation within a test, as well as within the
suite. Another form of test suite organization is based on system functionality and uses the quality attributes of
usability, reliability, and performance as categories for groups.&nbsp;You may choose to follow an iteration-based test
suite organization, instead.&nbsp;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><!-- END:sectionDescription,_Y-ABYKuSEdmhFZtkg1nakg -->
</body>
</html>