blob: e56583f8960df59f9634c0997d105504f8ea7d5c [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\guidances\checklists\test_script.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: test_script.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0Z9tMMlgEdmt3adZL5Dmdw CRC: 273197623 -->Test Script<!-- END:presentationName,_0Z9tMMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_0Z9tMMlgEdmt3adZL5Dmdw CRC: 4204877222 -->This checklist provides questions to verify that tests are created in a consistent and complete manner.<!-- END:briefDescription,_0Z9tMMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_DiPTsE_cEduqM_QlWBlZ_g CRC: 1963975593 -->Does the test script conform to the related test case<!-- END:name,_DiPTsE_cEduqM_QlWBlZ_g -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_DiPTsE_cEduqM_QlWBlZ_g CRC: 1951697416 -->Ensure that the test script conforms to the specification established in the test case if one is associated with the test
script.&nbsp; The test case captures the intent of the test; the test script must conform to this intent.<!-- END:sectionDescription,_DiPTsE_cEduqM_QlWBlZ_g -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_KS930Bg9EduxCP6DVVLxsA CRC: 1346387023 -->Is the test script testable<!-- END:name,_KS930Bg9EduxCP6DVVLxsA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_H-q58Bg9EduxCP6DVVLxsA CRC: 4065725125 -->Is the test script reusable<!-- END:name,_H-q58Bg9EduxCP6DVVLxsA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_H-q58Bg9EduxCP6DVVLxsA CRC: 1421571037 -->Ensure that your test scripts can be reused by designing your test scripts to maximize reuse.&nbsp; Promoting reuse takes
different forms depending on whether you are generating, programming, or recording test scripts.<!-- END:sectionDescription,_H-q58Bg9EduxCP6DVVLxsA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_5_92wE_cEduqM_QlWBlZ_g CRC: 850498300 -->Is the test script prescriptive and unambiguous<!-- END:name,_5_92wE_cEduqM_QlWBlZ_g -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_5_92wE_cEduqM_QlWBlZ_g CRC: 2116895210 -->Ensure that the test script represents clear instructions on how the test must be run and how the results should be
analyzed.&nbsp; While non-automated tests can be written in such a way that the tester can have leeway in how the test is
precisely run, there is no room for creativity in how the test results are to be analyzed for success or failure.<!-- END:sectionDescription,_5_92wE_cEduqM_QlWBlZ_g -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_La5wQBg9EduxCP6DVVLxsA CRC: 1149849764 -->Is the test script named consistently with your other test work products<!-- END:name,_La5wQBg9EduxCP6DVVLxsA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_La5wQBg9EduxCP6DVVLxsA CRC: 1404545553 -->Ensure that the naming of your test scripts is consistent with other test-related work products.&nbsp; For example, if you
are creating test classes for each of your test cases, ensure that the naming represents this relationship.&nbsp;
Alternatively, if you are building test scripts inside of a library, use a consistent naming convention to reflect the
library or libraries.<!-- END:sectionDescription,_La5wQBg9EduxCP6DVVLxsA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_Ng5zcBg9EduxCP6DVVLxsA CRC: 100638783 -->Does your test script provide test coverage<!-- END:name,_Ng5zcBg9EduxCP6DVVLxsA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_Ng5zcBg9EduxCP6DVVLxsA CRC: 2734995774 -->Ensure that your test scripts provide test coverage consistent with the system under test.<!-- END:sectionDescription,_Ng5zcBg9EduxCP6DVVLxsA -->
</body>
</html>