Skip to content

Latest commit

 

History

History
49 lines (35 loc) · 4.04 KB

README.md

File metadata and controls

49 lines (35 loc) · 4.04 KB

Access the app:

  • At this point users can see the welcome page , can browse trough bugs and features , can make queries (search input , filter by status or user) however users cannot see an item in detail , leave a comment, upvote or contribute towards any features

Register:

  • User has the option to create a new account or sign in with an existing account
  • To register the registration form must be filled in
  • if the registration form does not validate (eg. wrong email address, missing fields, username already in db , email already in db) the user will be redirected back to the form and asked to insert correct information
  • if the registration form validates the user will be logged in and redirected to welcome page

Login:

  • Users can log in by pressing “Log In” button from top right corner (accessing menu icon and then pressing “Log In “ button on small screen devices)
  • If sign-in details are incorrect the user will be redirected back to login page and informed that there are errors
  • If sign-in details are correct the user will be logged in and redirected to 'Current Bugs' page
  • Alternatively if the user has forgotten the login credentials they can be changed by pressing “Reset password” from login page where user can add their email address and if a user with that email address exists in db an email will be sent to that address with instructions to change the password

Bugs:

  • Click bugs form navigation bar , all registered bugs will be displayed in a descendant chronological order and “Report Bug” button will be displayed in navigation bar

  • Click see more on any of the registered bugs , at this point users can leave comments or upvote (I Have This Too) an item

  • If author is clicked the app will return a list will all bugs reported by the user

  • If status is clicked the app will return a list with all the bugs having the current status

  • If the user is also the author the options of edit and delete will be displayed

  • Click edit and a form will be displayed pre populated with the bug’s name and details to be edited

  • Click Update and the new values will be saved and a message will be displayed informing the user that item has been updated

  • Click remove bug and a modal(pop-up window) will open asking user for confirmation , if user selects ‘Cancel’ nothing will happen with the item , if User selects Delete the item and it’s related information (likes, views, comments) will be removed from db

Features:

  • Click features form navigation bar , all registered features will be displayed in a descendant chronological order and “Request a new feature“ button will be displayed in navigation bar.
  • Click see more on any of the requested features , at this point users can see all relevant information about the item (contributors, views , ammount left , amount collected , amount required ) and contribute towards implementing this feature and registered contributors will be shown at the bottom
  • Click Contribute to support this feature with any amount desired (min. £5) and then add to cart
  • If author is clicked the app will return a list will all features requested by the user
  • If status is clicked the app will return a list with all the requested features having the current status

Cart:

  • If user is authenticated cart icon will be displayed in top right corner with a badge displaying amount of features in cart (if any)
  • Click cart , if user hasn’t added any items a message will be shown informing the user that cart is empty , if the user has added items to cart they will be displayed as cards containing basic information and the amount user has chosen to contribute with, and options to alter the value or remove the item from cart

Checkout:

  • Click checkout and user will be redirected to payment page where the items and the amount are presented as well as payment and order form where all fields are required and if there are any errors (wrong input or invalid card details) the user will be informed of such errors and asked to correct them

Cookies:

  • In Order for authentication system to work cookies must be enabled