Iteration 4
Answers to comments for Iteration 3
-
In order to see the tests running, we gave the TA (rpglover64) access to our repository in GitHub. With that, he can access our Continuous Integration server in Travis.
The build for Iteration 4 is #43.
-
In order to the application running, we deployed it to Heroku. The currently deployed build is Iteration 4.
-
Indeed, the HTML documentation generated by YARD had a few glitches. That should be solved by now, thanks!
-
Our Rakefile does not point to a file outside the application. It’s self-contained. You can see that file here.
Iteration plan
Iteration 4
We installed a Continuous Integration server to make sure our tests are always run and ensure the quality of the product. We deployed the application to make it available to testers.
We implemented 15 unit tests for the Provider, Customer, and Affiliation classes, for example making sure that only Providers can create Affiliations, making sure that no one can see Affiliations that don’t belong to them, and that Providers can’t delete Affiliations that don’t belong to them. In addition, we implemented Business and ProviderProvacyConfiguration models, views, and controllers.
All planned classes have been added for the Slot-related model functionality.
We added styles to the application so that it’s easier on the eye.
We updated the database schema in order to enforce the presence of required fields, the uniqueness of some fields and foreign keys.
Iteration 5
We plan to implement search functionality. We also plan to take care of email verification via Devise and to take care of different Affiliation states.
Most remaining functionality will be added to existing Slot-related model classes, along with their unit tests.
We plan to add controllers and views so that Providers and Customers can manage their slots.
Iteration 6
Plan is to tie loose ends and support integration testing, as well as fix arising bugs.