| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:PracticeDescription 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="-MOoQ_OfD89D0nh4_1aSAuw" |
| name="rapid_testing,_9z1PgJ6NEdyQN-zRFaRrCQ" guid="-MOoQ_OfD89D0nh4_1aSAuw" changeDate="2008-08-07T14:33:18.844-0700" |
| version="7.5.0"> |
| <mainDescription><p> This practice requires a high degree of integration and high-bandwidth communication 
 |
| between developers and testers. Given these requirements, the following are 
 |
| the main conditions for applying this practice: </p>
 |
| <ul>
 |
| 
 |
| <li> <b>Coverage: </b>Component, feature, and subsystem (or system) testing 
 |
| </li>
 |
| <li> <b>Team considerations: </b>Small team with embedded tester or testers</li>
 |
| </ul></mainDescription> |
| <problem>This practice adopts testing throughout an iteration, concurrent with development. This prevents teams from compressing
 |
| testing into a separate activity at the end of an iteration or release. Concurrent testing reinforces the concept of
 |
| feature teams working in parallel.</problem> |
| <application><p> Use a multi-prong approach when you review this practice. You can start by 
 |
| focusing on the work products that will be produced or used during testing and 
 |
| then shift to the tasks involved in processing those artifacts. You might play 
 |
| different roles within your team. If you are a tester, then you will need to 
 |
| get a very good understanding of the artifacts, the tasks, and the guidelines 
 |
| supporting them. For a developer, the main points of interest are the artifacts 
 |
| used within this practice. </p>
 |
| <p> Start with the Test artifacts, read their description, and understand when 
 |
| they are used (produced or used), by whom, and which roles are mainly responsible: 
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <a class="elementLink" href="./../../../core.tech.common.extend_supp/workproducts/test_case_335C5DEA.html" guid="_0ZS-0MlgEdmt3adZL5Dmdw">Test Case</a>
 |
| </li>
 |
| <li>
 |
| <a class="elementLink" href="./../../../core.tech.common.extend_supp/workproducts/test_script_39A30BA2.html" guid="_0ZfMEMlgEdmt3adZL5Dmdw">Test Script</a>
 |
| </li>
 |
| <li>
 |
| <a class="elementLink" href="./../../../core.tech.common.extend_supp/workproducts/test_log_CBA2FDF4.html" guid="_0ZlSsMlgEdmt3adZL5Dmdw">Test Log</a>
 |
| </li>
 |
| </ul>
 |
| <p> Switch the focus to tasks and, depending on your main role within the team, 
 |
| review the associated guidelines, concepts and, if applicable, the tool-related 
 |
| guidance: </p>
 |
| <ul>
 |
| <li>
 |
| <a class="elementLink" href="./../../../practice.tech.concurrent_testing.base/tasks/create_test_cases_D39E98A1.html" guid="_0iwc0clgEdmt3adZL5Dmdw">Create Test Cases</a>
 |
| </li>
 |
| <li>
 |
| <a class="elementLink" href="./../../../practice.tech.concurrent_testing.base/tasks/implement_tests_26F00282.html" guid="_0jO98MlgEdmt3adZL5Dmdw">Implement Tests</a>
 |
| </li>
 |
| <li>
 |
| <a class="elementLink" href="./../../../practice.tech.concurrent_testing.base/tasks/run_tests_49698054.html" guid="_0jVEkMlgEdmt3adZL5Dmdw">Run Tests</a>
 |
| </li>
 |
| </ul></application> |
| </org.eclipse.epf.uma:PracticeDescription> |