Ironhack Web Development Bootcamp final project. Townbikes is a platform to rent your unused bicycle to travellers or find the best bicycle for your needs when you are travelling.
The three user flows that should always work - no matter what you change in your app.
The parts in (parenthesis) are not included in the happy path, but might be a good idea to test as well.
User signup flow
new User signs up
(receives confirmation email)*
(confirms his account)*
signs in in for the first time
searches for bikes in Barcelona
sees a map with all the bikes of Barcelona
User adds a bike flow
User adds (or edits) his location
adds a description of his bike
uploads a photo of his bike
saves the bike
(chooses the menu item to manage his bikes)
(edits his bike description)
(saves the bike)
Bike reservation flow
Renter searches for bikes in Barcelona
views the details of one bike
goes to the reservation page
fills in valid (or invalid) dates
saves the reservation
(is able to manage his pending reservations, including the new one)
the bike Owner sees on the overview of his bikes that he has a new pending reservation
and approves (or declines) the reservation
Writing acceptance/feature/behaviour specs (call them however you like) is the best solution. But if you don't find the time to do this, than test this workflow manually after every chunk of changes. (And Thursday midday and evening and Friday an hour before the presentation, if you are still committing changes by then.)
= in a feature spec you can not really test the sending/receiving of emails. You have to test the mailers in separation. In the feature spec you just check for the confirmation page ("an email has been sent to you") and than you have to confirm the user manually before singing in.
catburston
commented
10 years ago
The three user flows that should always work - no matter what you change in your app.
The parts in (parenthesis) are not included in the happy path, but might be a good idea to test as well.
Writing acceptance/feature/behaviour specs (call them however you like) is the best solution. But if you don't find the time to do this, than test this workflow manually after every chunk of changes. (And Thursday midday and evening and Friday an hour before the presentation, if you are still committing changes by then.)