| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-oW2j2l-rXqHeWPIgjPpbng" name="customer_tests,2.297945473205673E-305" guid="-oW2j2l-rXqHeWPIgjPpbng" changeDate="2006-11-10T09:32:51.048-0800" version="1.0.0"> |
| <mainDescription><a id="XE_xp__customer_tests" name="XE_xp__customer_tests"></a><a id="XE_customer_tests__practice_of" |
| name="XE_customer_tests__practice_of"></a><a id="XE_engineering_practices__customer_tests" |
| name="XE_engineering_practices__customer_tests"></a> |
| <h3> |
| Description |
| </h3> |
| <p> |
| One of the rights in the customer bill of rights tells the customer he will be able to see progress in the form of a |
| working system that passes repeatable tests that he specifies. These tests are what we call the Customer Tests. The |
| customer specifies one or more Customer Tests for each user story in the system, describing in detail how each story is |
| expected to work. Because the tests are put into executable form and are fully automated, they tell programmers what |
| needs to be done in a unambiguous way (tests pass or fail) and allow the customer to feel confident that the system is |
| meeting his needs. |
| </p> |
| <h3> |
| Benefits |
| </h3> |
| <ul> |
| <li> |
| Ability to see <b>tangible and verifiable progress</b>. |
| </li> |
| <li> |
| <b>Ultimate traceability</b>: the Customer Tests are executable system requirements. |
| </li> |
| <li> |
| <b>Repeatability</b>: because they are automated, the tests can be run at any time. |
| </li> |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |