| <?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\define_customer_test.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: define_customer_test.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,{DCDB57BE-4233-4CF8-90CE-70D6808F92B0} CRC: 2489882610 -->Define Customer Test<!-- END:presentationName,{DCDB57BE-4233-4CF8-90CE-70D6808F92B0} --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,-WgE0oiE2yddCOMnfzL25Gw CRC: 3909099008 --><a id="XE_define_customer_test__activity_definition" name="XE_define_customer_test__activity_definition"></a> |
| <ul> |
| <li> |
| Define the criteria under which the customer will deem a story complete. |
| </li> |
| </ul><!-- END:purpose,-WgE0oiE2yddCOMnfzL25Gw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_oGorMGE-EdqnIZeW8YpHcA CRC: 2118519414 -->Understand the Story <!-- END:name,_oGorMGE-EdqnIZeW8YpHcA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_oGorMGE-EdqnIZeW8YpHcA CRC: 3687733086 --><a id="Step1" name="Step1"></a> |
| <p> |
| Since the customer tests are automated, the customer has to be very specific about what the test will do. It is |
| impossible to do this if the customer does not understand the story in intimate detail from a user perspective. Writing |
| the customer tests will force the customer to go into all the details of the story. Stories must be testable. |
| </p><!-- END:sectionDescription,_oGorMGE-EdqnIZeW8YpHcA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_oGorMWE-EdqnIZeW8YpHcA CRC: 3682764237 -->Define Test Criteria <!-- END:name,_oGorMWE-EdqnIZeW8YpHcA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_oGorMWE-EdqnIZeW8YpHcA CRC: 2822317541 --><a id="Step2" name="Step2"></a> |
| <p> |
| Once the story is well understood and selected for the iteration, the automated customer tests are written. If the |
| customer team includes testers, the customer could communicate the test criteria to the tester. This can be verbal or |
| written. The criterion describes the tests for the normal and exceptional behavior of the system.<br /> |
| |
| </p><!-- END:sectionDescription,_oGorMWE-EdqnIZeW8YpHcA --> |
| </body> |
| </html> |
