During the refactoring of the web-api, it was found that all unit testcases regarding the weektemplate was commented-out, while there exists no file for the weektemplate, in the integration test project.
The weektemplate is not currently a utilized feature, however, it could add value to the project. If it is found to be a valuable feature that is to be utilized, both unit and integration test cases should be created for the controller.
If the feature is determined to be irrelevant, this issue should not concern the creation of test cases for the controller, but rather the removal of the controller, along with all its associations in the project, as keeping the deprecated code would only enforce a cluttered repository.
Depending on the outcome of the discussion regarding utilization of the feature, the workload of this issue is very different. However, it is still labelled a good-first-issue, as this should be established early on in the semester.
Possible Suggested Solution
Establish with the other groups of the semester if week template feature is to be utilized.
Either create test cases for the functionality, or remove the functionality, depending on the decisions of the groups.
Unit tests should be located in the WeekTemplateControllerTest file in the Giraf.UnitTest.Controllers directory.
Integration tests should be created in a new file in the Giraf.IntegrationTest.Tests directory.
Description
During the refactoring of the web-api, it was found that all unit testcases regarding the weektemplate was commented-out, while there exists no file for the weektemplate, in the integration test project.
The weektemplate is not currently a utilized feature, however, it could add value to the project. If it is found to be a valuable feature that is to be utilized, both unit and integration test cases should be created for the controller.
If the feature is determined to be irrelevant, this issue should not concern the creation of test cases for the controller, but rather the removal of the controller, along with all its associations in the project, as keeping the deprecated code would only enforce a cluttered repository.
Depending on the outcome of the discussion regarding utilization of the feature, the workload of this issue is very different. However, it is still labelled a good-first-issue, as this should be established early on in the semester.
Possible Suggested Solution