CSC/ECE 517 Fall 2019 - E1978. Fix issues related to deadlines and late policies: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 22: Line 22:


===Scope of the Project===
===Scope of the Project===
----
Issues described in the above section all exist in the Due Dates tab on the Edit Assignment page.
Issues described in the above section all exist in the Due Dates tab on the Edit Assignment page.
* '''Issue 1''' - Once this issue is fixed, the Due Dates tab while editing an assignment will have no ambiguity between "late policy" and "penalty policy", as "late policy" will be used exclusively.
* '''Issue 1''' - Once this issue is fixed, the Due Dates tab while editing an assignment will have no ambiguity between "late policy" and "penalty policy", as "late policy" will be used exclusively.

Revision as of 02:23, 11 November 2019

Fix issues related to deadlines and late policies

This page gives a description of the issues and the approach towards solving them in the E1978. Fix issues related to deadlines and late policies project.

Problem Description


Expertiza can automatically deduct points if a student is late in performing some action (e.g., submitting or reviewing). This is implemented by defining a new “late policy” and applying it to the assignment. Late policies are managed on the Due dates tab of assignment creation (or editing).


Issues with the Current Implementation


The current implementation of Expertiza has the following Issues:

  • Issue 1 - In the UI, the policy is sometimes called a “late policy” and sometimes a “penalty policy”. To avoid confusion, use “late policy” exclusively.
  • Issue 2 - Late policies cannot be created without raising an error.
  • Issue 3 - After creating a late policy, the “back” link does not take the user back to editing the assignment.
  • Issue 4 - The "+" and "-" buttons for Show/Hide Date Updater do not work. Expertiza has a way of adjusting due dates for a new assignment. If a new assignment is created by copying an old assignment, the due dates are copied too. It is likely that sometimes the same increment between due dates as in the old assignment (e.g., two days for the review phase, three days for resubmission, etc.) is wished. To avoid the need to edit all the deadlines manually, Expertiza has a date updater. However, it does not work.
  • Issue 5 - Neither late_policy.rb nor late_policies_controller.rb have any tests at all.


Scope of the Project


Issues described in the above section all exist in the Due Dates tab on the Edit Assignment page.

  • Issue 1 - Once this issue is fixed, the Due Dates tab while editing an assignment will have no ambiguity between "late policy" and "penalty policy", as "late policy" will be used exclusively.
  • Issue 2 - Once this issue is fixed, late policies can be created without raising the "The following error occurred while saving the penalty policy:" error.
  • Issue 3 - Once this issue is fixed, the back link after creating a late policy will rightly take the user to the Edit Assignment page.
  • Issue 4 - Once this issue is fixed, "+" and "-" buttons for Show/Hide Date Updater will work and update the dates as it is supposed to.
  • Issue 5 - The code coverage will definitely increase once tests for late_policy.rb and late_policies_controller.rb are written.


Approach



Test Plan


Automated Testing Using Rspec
We plan to create two new files, late_policy_spec.rb and late_policies_controller_spec.rb to test late_policy.rb and late_policies_controller.rb repesctively.

Coverage
To make sure we are covering all of our code (100%) with test cases we will use Ruby Code Coverage plugin of RubyMine and SimpleCov gem. After manually runnung the test file, the SimpleCov gem will highlight the lines of code which are being covered by our test cases in green color, and for those which are not being covered in red.



Milestones