CSC/ECE 517 Spring 2019 - Project E1931. Conflict notification: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 13: Line 13:
=What needs to be done=
=What needs to be done=


=UML Diagram=


=Files to be changed in this Project=
=Files to be changed in this Project=


* [https://github.com/expertiza/expertiza/blob/master/app/mailers/mailer.rb mailer.rb]
* [https://github.com/expertiza/expertiza/tree/master/config Config File]
* [https://github.com/expertiza/expertiza/blob/master/app/models/response.rb response.rb]


=Previous Project and its problems=


=Implementation=
=Implementation=

Revision as of 20:44, 6 April 2019

This wiki page is for the description of changes made under ECE517 SPRING 2019 PROJECT E1931 CONFLICT NOTIFICATIONS

Problem Statement

Current conflict notification sends an email to the instructor whenever two reviews for the same submission differ "significantly" on their scoring (the threshold is specified in the "Notification limit" on the Rubrics tab of assignment creation). Right now an email is sent at any such time one of these conflicts happen, however, it does not link to the particular review or submission which initiated the notification. The scope of this project is to send an email notification to instructor which contains links to two reviews (one of which is the newly submitted review) that differ by more than the notification limit where such a conflict has occurred. The email should state that a new conflicting review has been made.

Existing Feature Description

Currently this feature works as follows:

Whenever a student gives a review which differs by more than the threshold limit set,then a mail is sent to the instructor.

What needs to be done

Files to be changed in this Project

Previous Project and its problems

Implementation

[to be populated after coding is complete]

Test Plan

To test code implementation and correctness of the modified feature, we plan to do the following tests:-

  • Run and pass existing RSpec Tests
  • Develop New RSpec Tests for the new code
  • UI testing on the deployed project

Rspec Testing

[to be populated after coding is complete]

UI Testing

[to be populated after coding is complete]

References