Iteration 4
- Duty and degree of employ will be defined.
- Employ can cancel lessons, update information, confirm contract and put contract into effect.
- Customer has the option to buy a new contract, by the types of contracts.
- Having option to see a constant list of teachers.
- Having an option to contact with the gym / open an email at the user with the address of the gym inside the mail.
- Having an option to Access roads to the gym with google maps.
- Having the option to see history of lessons separated from list of future lessons .
- Having the option to read information about the importance of the health, sport and exercise.
###Information about the tasks:
Huboard
Issues
Our gitter
###Testing
optional tests on the main tasks of this iteration:
1.
test: register to a lesson
expected result:
-The registration is shown in the table LessonsOfClients.
-The registration is shown in the page "individual".
2.
test: choose a lesson in order to register to it.
expected result: The link of the lesson that was choosen will go to the right page
3.
test: press log in
expected result:
-all lessons that the client registered to will show
-a log out button will be shown
4.
test: press log out
expected result: home page will be shown (not logged-in)
5.
test: press on forgot password
expected result: an email will be sent to the user
6.
test: press on ourLessons in navbar
expected result: an explanation about this lesson will be shown
7.
test: pressing on the link register from log-in page
expected result: A register page will be shown
8.
test: pressing on the create user button
expected result: the new client will be added to table clients
###screenshot of the huboard before of this iteration
###screenshot of the huboard in the end of this iteration
.png)
###conclusion of the iteration:
We did not finish all the tasks of iteration 2, we preferred to have a wiki page for the iteration, so the tables we wanted to add in this iteration we put in the next one.
There is still the risk that we won't manage to accomplish the project till the end of the semester (which is really very close...) so all the team must be responsible and care about our project: checking mails twice a day (at least), doing their tasks from the huboard not in the last moment...
###Meeting and discussion summary, feedback of the customer: *We decided to organize the work in hierarchy order-there are some tasks that have to be done before another *We straightforward line with every body to make sure that we all know visual studio, c# , git etc.
##Project Summary Report
###Manual: