blob: 32a8ddd379c6d8e4d321af2aef6310897eaed6d1 [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\run_developer_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: run_developer_tests.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0iYCUMlgEdmt3adZL5Dmdw CRC: 1641130134 -->Run Developer Tests<!-- END:presentationName,_0iYCUMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_0iYCUMlgEdmt3adZL5Dmdw CRC: 2361968274 -->Run tests of the individual software components to verify that their internal structures work as specified.<!-- END:briefDescription,_0iYCUMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: keyConsiderations<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:keyConsiderations,_W6rc0Lv7EdmmUvZAZjqE3g CRC: 3718479650 --><p>
It is common to require that code pass all Developer tests before it can be delivered in an integrated build (see <a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/promoting_builds,_SM4YIL6dEdqti4GwqTkbsQ.html" guid="_SM4YIL6dEdqti4GwqTkbsQ">Guideline: Promoting Builds</a>).
</p>
<p>
Pair with the Tester during all steps of this task to gain insight on testing and quality considerations.
</p><!-- END:keyConsiderations,_W6rc0Lv7EdmmUvZAZjqE3g -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,_W6rc0Lv7EdmmUvZAZjqE3g CRC: 3502019315 -->To verify that the implementation works as specified.<!-- END:purpose,_W6rc0Lv7EdmmUvZAZjqE3g -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_MSnQsMP4EdmWKcx6ixEiwg CRC: 1641130134 -->Run Developer Tests<!-- END:name,_MSnQsMP4EdmWKcx6ixEiwg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_MSnQsMP4EdmWKcx6ixEiwg CRC: 1291443858 --><p>
Run the <a class="elementLink" href="./../../openup_basic/workproducts/developer_test,_0YuXEclgEdmt3adZL5Dmdw.html"
guid="_0YuXEclgEdmt3adZL5Dmdw">Developer Test</a>s. The procedure will vary, depending on whether the test is manual or
automated and whether additional test components are necessary,&nbsp;such as&nbsp;drivers or stubs.
</p>
<p>
To run the tests, you need to make sure that you have initialized the test environment with all necessary elements,
such as software, hardware, tools, data, and so on.
</p>
<p>
Automated tests will often update a <a class="elementLink"
href="./../../openup_basic/workproducts/test_log,_0ZlSsMlgEdmt3adZL5Dmdw.html" guid="_0ZlSsMlgEdmt3adZL5Dmdw">Test
Log</a>&nbsp;which you can evaluate to determine where your tests went wrong.
</p><!-- END:sectionDescription,_MSnQsMP4EdmWKcx6ixEiwg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_NkRF0MP4EdmWKcx6ixEiwg CRC: 2972435227 -->Evaluate test execution<!-- END:name,_NkRF0MP4EdmWKcx6ixEiwg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_NkRF0MP4EdmWKcx6ixEiwg CRC: 1624875948 --><p>
Evaluate the test execution by analyzing the test run.&nbsp;
</p>
<p>
Testing will&nbsp;complete either&nbsp;normally or abnormally.&nbsp; For correctly implemented tests, a normal
completion represents a passed test, though it could warrant additional examination of the test log to ensure&nbsp;the
test&nbsp;ran as expected.&nbsp; Abnormal termination could be premature termination or just a test that does not
complete as intended.
</p>
<p>
Review the test log to understand any reported failures, warnings, or unexpected results. The cause of the problem(s)
might be that the implementation element being tested is faulty, a problem with the developer tests, or a problem with
the environment.
</p><!-- END:sectionDescription,_NkRF0MP4EdmWKcx6ixEiwg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_SXPFkMP4EdmWKcx6ixEiwg CRC: 1739647734 -->Respond to test results<!-- END:name,_SXPFkMP4EdmWKcx6ixEiwg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_SXPFkMP4EdmWKcx6ixEiwg CRC: 94705704 --><p>
Determine the appropriate corrective action to recover from a "failed" developer test run. If the implementation
element under test is faulty, fix the problem if possible and rerun the tests. If the problem is serious and cannot be
immediately addressed, perform the task <a class="elementLink"
href="./../../openup_basic/tasks/request_change,_0mwzEclgEdmt3adZL5Dmdw.html" guid="_0mwzEclgEdmt3adZL5Dmdw">Request
Change</a> to report the defect. If the developer test is faulty fix the test and rerun the tests. If there was a
problem with the environment,resolve it and then rerun&nbsp;the tests.
</p>
<p>
When the developer tests pass, communicate the results. If the passing of these tests represent completion of a
requirement, this could involve updating the status of something on the <a class="elementLink"
href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html"
guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>.
</p><!-- END:sectionDescription,_SXPFkMP4EdmWKcx6ixEiwg -->
</body>
</html>