-
Notifications
You must be signed in to change notification settings - Fork 0
Project Report Deliverable 2
- Went over deliverable 2 requirements
- Assigned different roles to team members
- Fixed domain model from deliverable 1
- Fixed persistence layer
- Fixed the persistence layer tests
- Designed the REST API
- Implemented the REST methods
- Set up strategies for unit test
- Implemented the unit test
- Discussed strategies for integration test
- Tested our REST methods locally with postman
- Fixed bugs with REST API
- Added a few more tests
- Finalized documentation
- Build project with Travis CI and deploy to Heroku
- Discussed with other teams on how to implement the integration test
Based on the application requirements, our key design decision involved creating RESTful services that follows the necessary interactions between different views. We decided to categorize the REST methods depending on their accessibility from Coop-Admin, Employers and Academic program manager. In order to capture this design, we had to make edits to our existing domain design model from deliverable 1.
Apart from designing testing decisions which is separately reported in Software QA report, we also had to make decisions on how we want our model to be deployed. We initially wanted to connect Travis CI and Heroku both to Github. Due to some issues, we adopted the strategy of first connecting Travis CI to github and then connect Heroku to Travis at the time of app deployment.