| 18 | | <http://en.wikipedia.org/wiki/User_story> |
| 19 | | <A good User Story should answer the following questions:> |
| 20 | | <* Who the user is> |
| 21 | | <* What they want the solution to do for them?> |
| 22 | | <* Why they want it to do that? (goal)> |
| 23 | | <eg. A <type of user> wants the solution to <do something for them> so that <can achieve a goal>.> |
| | 18 | * Developers will run the test suite on making changes to the code to test if it works with the integration of the system. Developers may also see the test results mailed to the list to see the possible bugs introduced into the system. |
| | 19 | |
| | 20 | * People who want to deploy will run the test suite to check the functionality of the system. |
| | 21 | |
| | 22 | * The “bug marshalls” will review the test results mailed periodically by the CI Server and fix the bugs or log them. |
