TDD - oronsa/shoulder2shoulder GitHub Wiki
#Test Driven Development
Table of Contents
- Iteration Goals
- Iteration Roles
- Iteration Current Tasks
- Main Stories For The Current Iteration
- User Main View
- Admin Main View
- User Reports View
- Admin Options View
- Screenshots before Iteration
- Screenshots after Iteration
- Completion Points Assumptions
- Sprint Issues
- Client Feedback
- Team Meeting
- Weekly Summary
- Testing Methods
- Iteration Team Review
- Code Review
- Next iteration planning
Iteration Goals
This iteration's main goal will be to work on the admin and users module, meaning the creation of:
- User and Admin entry pages
- buttons with different views for each module
- Admin Options view (Including Token testing)
- User Reports view - The client will be able to examine part of the product, and give us feedback.
Iteration Roles:
- Back-end team: Oron Sason and Amir Lavi
- Front-end team: Shimri Peretz and Maen Abu-Gosh
Iteration Current Tasks:
Main Stories For The Current Iteration
-
User Main View
Creating the main page that the user will be seeing after validating the sign in
-
- Solomon is a family representative and have successfully Logged-In
-
- Solomon is automatically redirected to his designated main page (User's view)
-
- Solomon can scroll between his options in the navigation bar
-
-
Admin Main View
Creating the main page that the Admin will be seeing after validating the sign in
-
- Solomon is a family mentor-guide and have successfully Logged-In
-
- Solomon is automatically redirected to his designated main page (Admin's view)
-
- Solomon can scroll between his options in the navigation bar
-
-
User Reports View
Creating the Bills page which allow the user to fill in information regarding his expenses
-
- Given that Solomon is a family representative and have a bill to report
-
- Solomon can scroll to the bills view in his navigation bar
-
- Solomon can fill in the information regarding his report details
-
- Solomon can see a summary of all of his reports with details and editing options
-
-
Admin Options View
Creating the Option page for the Admin. Possible scenario:
-
- Solomon is a family mentor-guide and wants to generate a Token for a new family in the organization
-
- Solomon can scroll to the options view in his navigation bar
-
- Solomon can type the email designated to be Signed-Up in an input box and click "Generate Token"
-
- An e-mail with a link was sent to the family with instructions to how Signing-Up address that receives it
-
Screenshots before Iteration
https://github.com/oronsa/shoulder2shoulder/blob/master/Doc/Images/Iterations/iteration-2-before.jpg
Screenshots after Iteration
https://github.com/oronsa/shoulder2shoulder/blob/master/Doc/Images/Iterations/iteration-2-after.jpg
Completion Points Assumptions:
- Redirecting Modules functionality - 20 Points
- Admin's options page - 10 points
- Admin's navigation bar - 16 points
- User's navigation bar - 16 points
- Bills report page - 16 points
- Initialize front pages controllers, services and routing - 20 points Total: 104 points
Sprint issues
-
Team Meeting
-
Discussed and The main pages functionality and view
-
Some issues regarding the Modules switching when a user is logging-in
-
Weekly Summary
-
We overcome our frame-work issues and succeeded in routing data back and forth between the client and the server
-
Client Feedback
-
We updated the client over the phone regarding our progress and issues. We invited her to the next week meeting and Hopefully we would be able to show her a raw product.
Testing Methods
- Server side - Printing to console by "console.log(..)" results output to NodeJS command prompt
- Client side - Opening Goggle Chrome's developer console and applying breakpoints at desired line to view data during run time
- By the creation of mock objects by [mLab's] (https://mlab.com) we are able to simulate a real environment used by the actual users and see what happens when we retrieve their data from the database during run-time
Iteration Team Review
- Trying harder to work with full communication to allow synchronized code and efficiency
- Shimri and Maen work with better understanding on the client side
- Oron and Amir better focus on the server side functionality
Code Review
- Oron Sason : [issue] (https://github.com/oronsa/shoulder2shoulder/issues/20)
- Amir Lavi : issue
- Shimri Peretz : issue
- Maen Abu-Gosh :issue