This presentation is walk-through on how to convert user stories into working test suite, in the context of Ruby on Rails platform. Live coding part is available here: https://vimeo.com/54706598
We'll start by quickly examining the application we are going to work with and define our to-implement user story, along with scenarios and corresponding wireframes.
Next, I am going to talk about the process of mapping the information from user story into an end-to-end acceptance test. Having acceptance test prepared, we'll move to writing integration and unit tests. The focus will be put on how tester/developer is going through the stack of different test types, from acceptance, to integration and unit tests.
Finally, before we call it a day, we'll review each test type in terms of value it brings to the suite, asking ourselves a question: "do we really want to maintain *all* of these tests?"
11. • define task for other users
Monday, October 22, 12
12. • define task for other users
• see tasks assigned to myself,
only uncompleted
and they should be ordered according to priority
Monday, October 22, 12
13. • define task for other users
• see tasks assigned to myself,
only uncompleted
and they should be ordered according to priority
• take the most important task and complete
Monday, October 22, 12
14. see what's left on my plate,
and what should be done next
• define task for other users
• see tasks assigned to myself,
only uncompleted
and they should be ordered according to priority
• take the most important task and complete
Monday, October 22, 12
19. Outside-in thinking complements
any approach your teams may be taking to the
actual implementation of software, but it
changes how you
measure success.
A successful outside-in team does
a lot of learning and Tom Poppendieck
not much speculation. http://www.poppendieck.com/images/Tom-Web.jpg
Monday, October 22, 12