Exercise 9


Story 4: The user can display and update information about an iteration. The iteration display shows the iteration start and end dates, the projected team velocity, all stories assigned to the iteration, and the total of the estimates for those stories. For completed iterations, it displays the sum of the actuals for each story and the actual team velocity for that iteration. The user can update the estimated velocity, start date, and end date.

Q1:

For the above story from the XTrack application, identify which of the following details you would a) assume responsibility for defining yourself, b) ask for confirmation on, or c) ask open-ended questions about:

  • Constraints on the allowable inputs for start and end dates during update.

  • What should happen when invalid data is input during update.

  • The units in which to display the velocity, estimates, and actual totals.

  • What determines that an iteration is complete.

  • Which information will be included about each story.

  • What happens when a story is moved from one iteration to another.

  • Can completed stories in a completed iteration be moved to another iteration?

  • The order in which the stories appear.

Q2:

For the above story, identify some additional details based on

  • The happy path

  • The sad path

  • The bad path

Q3:

Based on risk, where would you focus the most attention in designing tests for the following first four XTrack stories?

Story 1: Be able to create, read, and update a story via a Web interface. The data fields in a story are number, name, author, description, estimate, iteration, timestamps, and state.

Story 2: The user can provide an estimate for how long it will take to implement a story, prioritize the story, and assign the story to an iteration.

Story 3: The user can create, update, display, and delete a task. A task has a name, a description, assignee, estimate, actual time spent, state, and created/updated timestamps.

Story 4: The user can display and update information about an iteration. The iteration display shows the iteration start and end dates, the projected team velocity, all stories assigned to the iteration, and the total of the estimates for those stories. For completed iterations, it displays the sum of the actuals for each story and the actual team velocity for that iteration. The user can update the estimated velocity, start date, and end date.



Testing Extreme Programming
Testing Extreme Programming
ISBN: 0321113551
EAN: 2147483647
Year: 2005
Pages: 238

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net