CSC/ECE 517 Spring 2022 - E2237: Grading audit trail

From Expertiza_Wiki
Jump to navigation Jump to search

Team

Students

  • Bhuwan Bhatt (brbhatt)
  • Soumyadeep Chatterjee (schatte5)
  • Kelly Fleming (kflemin3)
  • Karthik Gopala Sundaresan (kgopala3)

Mentor

  • Kai Xiao (yxiao28)

Topic Overview

Prior Work

The previous team's wiki write-up contains detailed information regarding this feature. A summary of the desired functionality is presented below:


Overview of Major Changes

A new table was added to the database (grading_history), along with the corresponding model (grading_history.rb) and controller (grading_history_controller.rb).

Two models for specific types of histories were added: review_grading_history.rb, and submission_grading_history.rb.

A view for displaying the grading history of a particular assignment or review was added (index_html.erb).

Modifications to Existing Files

app/controllers/grades_controller.rb
A grading history record is created for every edit to a submission's grade.
app/controllers/review_mapping_controller.rb
A grading history record is created for every edit to a review's grade.
app/views/assignments/list_submissions.html.erb
A link to access a submission's grade history is shown in the submissions table.
app/views/reports/_review_report.html.erb
A link to access a review's grade history is shown in the review report table.

Testing (NOTE: should probably remove this from here)

Functional tests ensuring specific method calls are made were added.

functional tests added to these files
spec/controllers/grades_controller_spec.rb
spec/controllers/review_mapping_controller_spec.rb
spec/controllers/grading_histories_controller_test.rb

A feature test ensuring that correct grading history is shown in chronological order was added.

feature test handled by these two files
spec/features/grade_histories_spec.rb
spec/features/helpers/grade_histories_helper.rb

Whenever an instructor submits a new grade, or edits an existing grade, the grading_history_controller saves a new history entry to the database.

Statement of Problem

There are three areas of focus for this project:

System Crashes and Object Creation

First, the work done by the previous team results in the system crashing when the tests are being executed; as a result, automated unit testing does not succeed. Our goal in this regard is to ensure that the tests are successfully executed for all test cases, with the appropriate outcome and coverage reports visible to the user.

Second, testing efforts to this point have used static, pre-created objects; this is due to issues with object creation. Our goal in this aspect is to ensure that the creation of new test objects, namely Student Accounts, Assignments, and Project Bids is successful.

Changes to Grading History Table

The grading history table is earmarked for certain changes:
a. Extract Student ID from the table, and ensure that it is shown in the header
b. Extract Assignment ID from the table, and ensure that it is shown in the header

Code and Documentation Goals

Add reasonings and data flow structures/UML diagrams that detail the changes that have been made, as well as any comments on why certain files needed to be modified. These will be completed from these perspectives:
a. From a data flow point of view
b. From a function point of view
c. With comment in code

Plan and List of Work Done

General Design Goals

Specific Tasks Completed

Initial Implementation

Final Implementation

Testing

Video Demonstration

will be added for the final submission

Testing Goals and Test Objects

Drawing from the project objectives: 1. Verify that Student Accounts can be created and are saved to the database. 2. Verify that Assignments can be created and are saved to the database. 3. Verify that Project Bids can be created and are saved to the database. 4. Ensure that Student ID is shown in the header via RSpec, and verify via manual UI testing 5. Ensure that Assignment ID is shown in the header via RSpec, and verify via manual UI testing


General Testing Plan

RSpec Unit Tests

Manual UI Tests

Discussion with mentor in progress to determine if UI Automation testing is in scope

Regression Testing

In order to ensure complete coverage, testing of the changes done between the end of last semester and this project was done.

Note to team: need to edit this after investigation


1. Investigate if this is testable using Capybara
2. Get the specific format requirement for the title, and assert that it's there. Ensure that this doesn't appear anywhere else (possible via ensuring count is 1)
3. Procure specific required column width, and assert that this is the value in the file (the constant)
4. Inquire with mentor about comment requirement and conflicts
5. Inquire with mentor regarding white space constraints
6. Inquire why the revert is needed, what is breaking and why
7. Ask mentor where this file is being called, and if functionality needs to be moved elsewhere.
8. Complete Design Document to reflect these changes.

Conclusions and Future Work

Thoughts on Comprehensive Testing and Scope

Test Plan Document (SoP)

Conclusion

Useful Links

Previous team's Expertiza GitHub pull request

Previous team's wiki write-up

E1934 implementation video walkthrough