blob: 8b05f3c505e8d29f5dd78609fc41ea9e6425ee4b [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>\xp\tasks\integrate_system.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: integrate_system.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,{70FEC254-8555-4844-AD82-68367E25F082} CRC: 3886483177 -->Integrate and Build<!-- END:presentationName,{70FEC254-8555-4844-AD82-68367E25F082} -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,--tP2hgRfEkZPGYvy1y0GZQ CRC: 1359296844 --><a id="XE_integrate_and_build__activity_definition" name="XE_integrate_and_build__activity_definition"></a>
<ul>
<li>
To produce a runnable executable of the application under development that can be used to evaluate progress and
provide feedback
</li>
</ul><!-- END:purpose,--tP2hgRfEkZPGYvy1y0GZQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_oE9QMGE-EdqnIZeW8YpHcA CRC: 851040656 --> Run All Unit Tests for the System <!-- END:name,_oE9QMGE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_oE9QMGE-EdqnIZeW8YpHcA CRC: 873258984 --><a id="Step1" name="Step1"></a>
<p>
While you and your pair partner are working on a task, you run unit tests to make sure you are not introducing side
effect defects. As a system evolves, it may become impractical to run all the unit tests for the system for every
change made. In this case, you may choose a subset of the unit tests to run after every code change. When a task is
completed or you feel that you have a piece you can integrate or you are uncertain for any reason, run all of the unit
tests for the system.
</p><!-- END:sectionDescription,_oE9QMGE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_oE9QMWE-EdqnIZeW8YpHcA CRC: 3886211169 --> Check in Code <!-- END:name,_oE9QMWE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_oE9QMWE-EdqnIZeW8YpHcA CRC: 2110781309 --><a id="Step2" name="Step2"></a>
<p>
If all of the unit test in the system passed, check in your code and produce a system build.
</p><!-- END:sectionDescription,_oE9QMWE-EdqnIZeW8YpHcA -->
</body>
</html>