| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription 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="-fm-gBePbdl_WMsE5NxEreQ" name="automate_acceptance_test,{E614ED93-AE72-4FD1-B459-C508CE1C536F}" guid="-fm-gBePbdl_WMsE5NxEreQ" version="1.0.0"> |
| <sections xmi:id="_oNCOIGE-EdqnIZeW8YpHcA" name=" General " guid="_oNCOIGE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Prep" name="Prep"></a> |
| <p> |
| XP teams represent detailed requirements as automated customer tests. Automating the tests insures they are detailed, |
| unambiguous, and executable. Typically, each acceptance criteria is translated into at least one automated test. |
| </p> |
| <p> |
| There are lots of ways to do this: |
| </p> |
| <ul> |
| <li> |
| For a batch program reading inputs and producing outputs: create test input files, capture actual output, and |
| compare it against expected output. |
| </li> |
| <li> |
| Write functional tests as programs. You can use a unit testing framework as a base or create a little scripting |
| language the programmers can use. |
| </li> |
| <li> |
| Allow the customer to easily specify tests (spreadsheets, flat text files) and create a small tool to read the |
| input and expected output. The tool runs the input against the system and checks that the actual output matches the |
| expected output. |
| </li> |
| <li> |
| Build an input recorder to allow customers to define the tests. |
| </li> |
| <li> |
| Use simple file-based tools to check the results. |
| </li> |
| </ul> |
| <p> |
| It is important to build the automation simply and incrementally as you need it. It is too easy to lose control and |
| invest too much time in test automation instead of business value. Don't overdo it. |
| </p></sectionDescription> |
| </sections> |
| <purpose><a id="XE_automate_customer_test__activity_definition" name="XE_automate_customer_test__activity_definition"></a> |
| <ul> |
| <li> |
| Transform the acceptance criteria of a user story into executable form. |
| </li> |
| </ul></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |