Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2023 - E2337. Reimplement node hierarchy

2023-04-13T00:21:40Z

Ashon: /* Class Hierarchy */

==Introduction==

The node models in Expertiza act as a kind of Decorator for underlying database models. They allow relevant information to be accessed and displayed readily. Nodes are hierarchical; they can have arbitrarily deep trees of child and parent nodes. This hierarchical structure allows code reuse and custom implementations to exist alongside default implementations to keep functionalities modular and isolated, minimizing the risk of breakage.

===Problem Statement===

The existing code for the node hierarchy is largely sufficient, but the documentation and testing are lacking. This project aims to reimplement the existing code but with better naming conventions, documentation, and more comprehensive testing.

Goals:

* Improve method naming conventions where possible.
* Refactor specific implementations, such as self.get(), where possible to provide uniformity and avoid DRY issues.
* Add appropriate comments in existing code in each file, which makes it easier to understand the functionality.
* Create a method to return true/false based on courses.private [Line 46 & 48 in course_node.rb].
* Update tests to ensure more comprehensive coverage.

===Class Hierarchy===

Method names listed in red are existing functions that will be renamed

[[File:UML_Diagram_nodes.jpg]]

The Node model is the base class from which all other nodes inherit. The children of the node model are AssignmentNode, CourseNode, FolderNode, QuestionnaireNode, QuestionnaireTypeNode, TeamNode, and TeamUserNode. Node classes take advantage of polymorphism to interact and create the hierarchy, and specific functionality is implemented in the child classes.

===Test Plan===

{| class="wikitable"
|+ course_node_test.rb
|-
! Test No. !! Method !! Description
|-
| 1 || create_course_node || Tests if a course node is saved with data
|-
| 2 || get_course_query_conditions || Tests when show and current user are set and you are not a TA
|-
| 3 || table || Tests that the table returns courses
|-
| 4 || get_course_query_conditions || Tests when show and current user are set and you are a TA
|-
| 5 || get_courses_managed_by_user || Tests that user id is returned when you are not a TA
|-
| 6 || get_parent_id || Tests returning id of parent folder when parent is found
|-
| 7 || get_parent_id || Tests returning nil when parent is not found
|-
| 8 || get_children || Tests returning assignment node when children are found
|-
| 9 || get_private || Tests whether the course returned is private
|-
| 10 || get_survey_distribution_id || Tests that the course returns a survey distribution id
|}

{| class="wikitable"
|+ questionnaire_node_test.rb
|-
! Test No. !! Method !! Description
|-
| 1 || get || Tests the questionnaire returns when the user is a teaching assistant
|-
| 2 || get || Tests the questionnaire returns when the user is not a teaching assistant
|-
| 3 || get || Tests the questionnaire returns with association with student when the user is not a teaching assistant and show is enabled
|-
| 4 || get || Tests the questionnaire returns with association with student when the user is a teaching assistant and show is enabled and parent id is enabled
|-
| 5 || table || Tests the return of name of table
|-
| 6 || is_leaf || Test whether the node is a leaf
|-
| 7 || get_modified_date || Test when the questionnaire was last changed
|-
| 8 || get_created_date|| Test when the questionnaire was created
|-
| 9 || get_private || Test when the questionnaire is private
|-
| 10 || get_instructor_id || Test whether the instructor id is associated with questionnaire
|-
| 11 || get_name || Test whether the questionnaire name is returned
|-

|}

{| class="wikitable"
|+ questionnaire_type_node_test.rb
|-
! Test No. !! Method !! Description
|-
| 1 || get_name || Tests the name of the table is returned
|-
| 2 || get || Tests the nodes that are associated with the parent
|-
| 3 || get_partial_name || Tests the return of the questionnaire_type_actions
|-
| 4 || get || Tests the return of the name of the associated tree folder
|-
| 5 || get_children || Tests the return of the children

|}

{| class="wikitable"
|+ folder_node_test.rb
|-
! Test No. !! Method !! Description
|-
| 1 || get_name || Tests the name of the folder is found
|-
| 2 || get|| Tests fetching of folder node where type is unknown and the parent is not known
|-
| 3 || get_partial_name || Tests the partial name is returned correctly
|-
| 4 || get_child_type || Tests the return of child type from the tree folder
|-
| 5 || get_children || Tests the return of children with the given parameters

|}

{| class="wikitable"
|+ assignment_node_test.rb
|-
! Test No. !! Method !! Description
|-
| 1 || table || Tests the return of the assignments table
|-
| 2 || get || Tests the list of assignment nodes are returned based on query parameters
|-
| 3 || is_leaf || Tests if the node is a leaf
|-
| 4 || belongs_to_course || Tests if the node belongs to course
|-
| 5 || get_instructor_id || Tests the instructor id is returned
|-
| 6 || retrieve_institution_id || Tests the institution id is returned
|-
| 7 || get_private || Tests the private field is returned
|-
| 8 || get_max_team_size || Tests the max team size is returned
|-
| 9 || get_is_intelligent || Tests the is_intelligent field is returned
|-
| 10 || get_require_quiz || Tests the get_required_quiz field is returned
|-
| 11 || get_allow_suggestions || Tests the get_allow_suggestions field is returned
|-
| 12 || get_teams || Tests the get_teams field is returned
|-
|}

{| class="wikitable"
|+ team_node_test.rb
|-
! Test No. !! Method !! Description
|-
| 1 || table || Tests the teams table is returned
|-
| 2 || get || Tests that the team node is fetched by parent id
|-
| 3 || get_name || Tests the name is returned correctly by ip address
|-
| 4 || get_children || Tests the children of the node are fetched properly
|-

|}

{| class="wikitable"
|+ team_user_node_test.rb
|-
! Test No. !! Method !! Description
|-
| 1 || table || Tests the teams table is returned
|-
| 2 || get_name || Tests that the team user node is fetched by parent id
|-
| 3 || get || Tests the name is returned correctly by ip address
|-
| 4 || is_leaf || Tests that the node is a leaf
|-

|}

CSC/ECE 517 Spring 2023

2023-04-05T21:29:56Z

Ashon: /* OSS Projects */

== OSS Projects ==
[[CSC/ECE 517 Spring_2023 -E2306. Refactor user_controller.rb, user.rb and its child classes]]

[[CSC/ECE 517 Spring_2023 - E2320. Reimplement the Question hierarchy]]

[[CSC/ECE 517 Spring_2023 - E2312 + E2313. Reimplement response.rb and responses_controller.rb]]

[[CSC/ECE 517 Spring_2023 - NTNX-1. Support provisioning MongoDb via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring_2023 - E2316. Reimplement sign_up_sheet_controller.rb]]

[[CSC/ECE 517 Spring_2023 - E2315. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb]]

[[CSC/ECE 517 Spring_2023 - E2339. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb (Project 4)]]

[[CSC/ECE 517 Spring_2023 - E2323. Refactor DueDate functionality from assignment.rb]]

[[CSC/ECE 517 Spring 2023 - E2317: Reimplement participant.rb]]

[[CSC/ECE 517 Spring 2023 - E2314. Reimplement the response map hierarchy]]

[[CSC/ECE 517 Spring 2023- NTNX-4. Extend NDB operator provision postregresql aws]]

[[CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController]]

[[CSC/ECE 517 Spring 2023 - E2305. Grading audit trail]]

[[CSC/ECE 517 Spring 2023 - E2309. Refactor Node model and its subclasses]]

[[CSC/ECE 517 Spring 2023 - NTNX-2. Support provisioning mySQL databases via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring 2023 - E2300. Refactor E1858. Github metrics integration]]

[[CSC/ECE 517 Sping 2023 - E2322: Refactor Questionnaire View to display Bookmark Rating]]

[[CSC/ECE 517 Spring 2023 - NTNX-3. Refactor models to keep profiles (software, compute, network, etc) as optional and use default if not specified]]

[[CSC/ECE_517_Spring_2023_-_E2301._Refactor_review_maping_helper]]

[[CSC/ECE_517_Spring_2023_-_E2337._Reimplement_node_hierarchy]]

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:48:44Z

Ashon: /* Testing */

In order to accommodate issues with another team, our team picked up another member and did both projects. The summaries of the projects are combined here to reflect that. Note that the requirements on the original projects are being treated more loosely to account for the additional work.

= E2312 Reimplement Response =

== Summary of Changes ==

The previous version of response.rb was described as "a mess." The goal of E2312 was to reimplement it to follow better coding standards.

* Made method names clearer, many method names were opaque and did not properly convey their functionality. For example, add_table_rows:
[[File:add_table_rows.png]]
* Moved many functionalities to mixins or helper classes to not violate the Single-Responsibility Principle (also many comments with no useful information)
[[File:scores_response.png]]
* Reduced usage of class methods

== Functionality Moved ==

This section covers the functionality that was moved out of the response model.

=== Score Calculation ===

Score calculation is not inherently tied to the idea of a response.
Any object with multiple scores could take advantage of a mixin that provided methods to do calculations on those scores. This created multiple responsibilities for the response object and encouraged non-DRY code.
Functionality for calculating total, average, and maximum scores were all moved to a new Scorable mixin which can be leveraged by other models moving forward.

Previously that functionality was implemented directly on the response class:

[[File:aggregate_score.png]]

Now it exists in a mixin, as demonstrated with this snippet:

[[File:scorable_mixin.png]]

=== Emails ===

The response model provided a method for creating emails. This was moved to a new MailMixin, which can be expanded to provide email functionality to more models in the future. This removed additional responsibilities to help maintain the Single Responsibility principle and helps move email-based code toward a more DRY implementation in the future.

[[File:mail_mixin.png]]

=== Metrics ===

The response model provided a method for getting the volume of review comments on a response. This was moved to a ReviewCommentMixin as it is not necessarily specific to response models. This helps maintain the Single-Responsibility Principle for the response model.

[[File:review_comment.png]]

== Improved Naming ==

Fix instances of bad and opaque naming, like aggregate_question_score(), add_table_row(), and concatenate_all_review_comments() (which does more than the name implies).

== Test Plan ==

Many other parts of the software were stubbed out in the implementation project in order to run unit tests. The existing test suite was run against the implementation and passed successfully. Due to the fact that this project has no front end, the professor asked us to record a video of tests being run to demonstrate functionality, which is linked in the project submission.

Test cases:

* Total score of a review
* Average scores across a review when the maximum score is 0
* Average scores across a review when the maximum score is not 0
* Maximum scores for a response when there are no points available
* Maximum scores for a response standard case
* Volume of review comments
* Concatenating all review comments

= E2313 Reimplement Response Controller =

== Summary of Changes ==

The previous version of response_controller.rb was too long. It included too many functions besides the basic CRUD methods. The goal of E2313 was to reimplement it to follow better coding standards.

* Made method name to follow plural convention not singular convention.
* Moved many functionalities to mixins or helper classes

== Functionality Moved ==

This section covers the functionality that was moved out of the responses controller.

=== Authentication and Authorization ===

There were authentication and authorization methods in the response controller. These were moved to authorization helper.

=== Redirect ===

There was a redirect function that helps redirect by params. It is moved to response helper.

=== Sort Reviews ===

There was functionality to sort reviews. We made a new function named sortReviews to perform this functionality and placed it in the response model

== Singular convention to Plural convention ==

There were some function and classes that followed singular conventions, but were changed to follow plural convention.

[[File:plural.png]]

[[File:authorization_helper.png]]

== Reducing code ==

There were multiple method invocations to set parameters (assign_action_parameters, set_content). We used the macro, before_action, so that we reduced the number of calls for these methods.

[[File:macro.png]]

== Testing ==

1. Response Deletion

- Verify that if the response is enabled for team reviewing, but lock is not existent, proceed to lock response
- Verify that if the response is not team review enabled, proceed to delete the response and redirect the user

2. Response Edit

- Verify preparing already existent response for editing purposes
- Verify creating new response if non-existent for editing purposes

3. Response Update

- Verify submitted response contains the new updated fields upon submission

4. Response New Feedback

- Redirect user to the new feedback page with relevant Response, Participant, and FeedbackResponseMap data
- If a review is not found, redirect user to the root path

5. Response Create

- If Response is found by query parameter, update with additional comments and instantiate answers
- If Response is not found by query parameter, create new Response instance with additional comments and instantiate answers

6. Response Save

- With the found ResponseMap, save with existing query parameters

7. Initialize Answers

- Verify answers are created from a passed-in list of questions

8. Questionnaire from Response Map

- Verify if current map type is ReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is SelfReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is MetareviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is TeammateReviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is FeedbackResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is CourseSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is AssignmentSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is GlobalSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is BookmarkRatingResponseMap, set questionnaire based on if assignment is duty based

9. Assign Action Parameters

- Verify when action is edit, header and next_action are assigned as "Edit" and "update" respectively
- Verify when action is new, header and next_action are assigned as "New" and "create" respectively

10. Setting Response

- Verify response and map instances are set based on the query parameter passed in

11. Toggling permission

- Verify a given response is found and its visibility attribute is toggled to its corresponding opposite value

12. Show Calibration Results for Student

- Verify with the given query parameters: assignment_id, calibration_response_map_id, review_response_map_id, that the assignment, calibration response, review response and questions instances are set correctly

[[File:Screenshot 2023-03-27 at 10.40.26 PM.png]]

[[File:Answers.png]]

File:Answers.png

2023-03-28T02:48:03Z

Ashon:

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:43:29Z

Ashon: /* Testing */

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:43:13Z

Ashon: /* Testing */

File:Screenshot 2023-03-27 at 10.40.26 PM.png

2023-03-28T02:42:54Z

Ashon: Ashon uploaded a new version of File:Screenshot 2023-03-27 at 10.40.26 PM.png

File:Screenshot 2023-03-27 at 10.40.26 PM.png

2023-03-28T02:41:57Z

Ashon:

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:35:03Z

Ashon: /* Reducing code */

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:34:42Z

Ashon: /* Singular convention to Plural convention */

In order to accommodate issues with another team, our team picked up another member and did both projects. The summaries of the projects are combined here to reflect that. Note that the requirements on the original projects are being treated more loosely to account for the additional work.

= E2312 Reimplement Response =

== Summary of Changes ==

The previous version of response.rb was described as "a mess." The goal of E2312 was to reimplement it to follow better coding standards.

* Made method names clearer, many method names were opaque and did not properly convey their functionality. For example, add_table_rows:
[[File:add_table_rows.png]]
* Moved many functionalities to mixins or helper classes to not violate the Single-Responsibility Principle (also many comments with no useful information)
[[File:scores_response.png]]
* Reduced usage of class methods

== Functionality Moved ==

This section covers the functionality that was moved out of the response model.

=== Score Calculation ===

Score calculation is not inherently tied to the idea of a response.
Any object with multiple scores could take advantage of a mixin that provided methods to do calculations on those scores. This created multiple responsibilities for the response object and encouraged non-DRY code.
Functionality for calculating total, average, and maximum scores were all moved to a new Scorable mixin which can be leveraged by other models moving forward.

Previously that functionality was implemented directly on the response class:

[[File:aggregate_score.png]]

Now it exists in a mixin, as demonstrated with this snippet:

[[File:scorable_mixin.png]]

=== Emails ===

The response model provided a method for creating emails. This was moved to a new MailMixin, which can be expanded to provide email functionality to more models in the future. This removed additional responsibilities to help maintain the Single Responsibility principle and helps move email-based code toward a more DRY implementation in the future.

[[File:mail_mixin.png]]

=== Metrics ===

The response model provided a method for getting the volume of review comments on a response. This was moved to a ReviewCommentMixin as it is not necessarily specific to response models. This helps maintain the Single-Responsibility Principle for the response model.

[[File:review_comment.png]]

== Improved Naming ==

Fix instances of bad and opaque naming, like aggregate_question_score(), add_table_row(), and concatenate_all_review_comments() (which does more than the name implies).

== Test Plan ==

Many other parts of the software were stubbed out in the implementation project in order to run unit tests. The existing test suite was run against the implementation and passed successfully. Due to the fact that this project has no front end, the professor asked us to record a video of tests being run to demonstrate functionality, which is linked in the project submission.

Test cases:

* Total score of a review
* Average scores across a review when the maximum score is 0
* Average scores across a review when the maximum score is not 0
* Maximum scores for a response when there are no points available
* Maximum scores for a response standard case
* Volume of review comments
* Concatenating all review comments

= E2313 Reimplement Response Controller =

== Summary of Changes ==

The previous version of response_controller.rb was too long. It included too many functions besides the basic CRUD methods. The goal of E2313 was to reimplement it to follow better coding standards.

* Made method name to follow plural convention not singular convention.
* Moved many functionalities to mixins or helper classes

== Functionality Moved ==

This section covers the functionality that was moved out of the responses controller.

=== Authentication and Authorization ===

There were authentication and authorization methods in the response controller. These were moved to authorization helper.

=== Redirect ===

There was a redirect function that helps redirect by params. It is moved to response helper.

=== Sort Reviews ===

There was functionality to sort reviews. We made a new function named sortReviews to perform this functionality and placed it in the response model

== Singular convention to Plural convention ==

There were some function and classes that followed singular conventions, but were changed to follow plural convention.

[[File:plural.png]]

[[File:authorization_helper.png]]

== Reducing code ==

There were multiple method invocations to set parameters (assign_action_parameters, set_content). We used the macro, before_action, so that we reduced the number of calls for these methods.

== Testing ==

1. Response Deletion

- Verify that if the response is enabled for team reviewing, but lock is not existent, proceed to lock response
- Verify that if the response is not team review enabled, proceed to delete the response and redirect the user

2. Response Edit

- Verify preparing already existent response for editing purposes
- Verify creating new response if non-existent for editing purposes

3. Response Update

- Verify submitted response contains the new updated fields upon submission

4. Response New Feedback

- Redirect user to the new feedback page with relevant Response, Participant, and FeedbackResponseMap data
- If a review is not found, redirect user to the root path

5. Response Create

- If Response is found by query parameter, update with additional comments and instantiate answers
- If Response is not found by query parameter, create new Response instance with additional comments and instantiate answers

6. Response Save

- With the found ResponseMap, save with existing query parameters

7. Initialize Answers

- Verify answers are created from a passed-in list of questions

8. Questionnaire from Response Map

- Verify if current map type is ReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is SelfReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is MetareviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is TeammateReviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is FeedbackResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is CourseSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is AssignmentSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is GlobalSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is BookmarkRatingResponseMap, set questionnaire based on if assignment is duty based

9. Assign Action Parameters

- Verify when action is edit, header and next_action are assigned as "Edit" and "update" respectively
- Verify when action is new, header and next_action are assigned as "New" and "create" respectively

10. Setting Response

- Verify response and map instances are set based on the query parameter passed in

11. Toggling permission

- Verify a given response is found and its visibility attribute is toggled to its corresponding opposite value

12. Show Calibration Results for Student

- Verify with the given query parameters: assignment_id, calibration_response_map_id, review_response_map_id, that the assignment, calibration response, review response and questions instances are set correctly

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:34:23Z

Ashon: /* Singular convention to Plural convention */

In order to accommodate issues with another team, our team picked up another member and did both projects. The summaries of the projects are combined here to reflect that. Note that the requirements on the original projects are being treated more loosely to account for the additional work.

= E2312 Reimplement Response =

== Summary of Changes ==

The previous version of response.rb was described as "a mess." The goal of E2312 was to reimplement it to follow better coding standards.

* Made method names clearer, many method names were opaque and did not properly convey their functionality. For example, add_table_rows:
[[File:add_table_rows.png]]
* Moved many functionalities to mixins or helper classes to not violate the Single-Responsibility Principle (also many comments with no useful information)
[[File:scores_response.png]]
* Reduced usage of class methods

== Functionality Moved ==

This section covers the functionality that was moved out of the response model.

=== Score Calculation ===

Score calculation is not inherently tied to the idea of a response.
Any object with multiple scores could take advantage of a mixin that provided methods to do calculations on those scores. This created multiple responsibilities for the response object and encouraged non-DRY code.
Functionality for calculating total, average, and maximum scores were all moved to a new Scorable mixin which can be leveraged by other models moving forward.

Previously that functionality was implemented directly on the response class:

[[File:aggregate_score.png]]

Now it exists in a mixin, as demonstrated with this snippet:

[[File:scorable_mixin.png]]

=== Emails ===

The response model provided a method for creating emails. This was moved to a new MailMixin, which can be expanded to provide email functionality to more models in the future. This removed additional responsibilities to help maintain the Single Responsibility principle and helps move email-based code toward a more DRY implementation in the future.

[[File:mail_mixin.png]]

=== Metrics ===

The response model provided a method for getting the volume of review comments on a response. This was moved to a ReviewCommentMixin as it is not necessarily specific to response models. This helps maintain the Single-Responsibility Principle for the response model.

[[File:review_comment.png]]

== Improved Naming ==

Fix instances of bad and opaque naming, like aggregate_question_score(), add_table_row(), and concatenate_all_review_comments() (which does more than the name implies).

== Test Plan ==

Many other parts of the software were stubbed out in the implementation project in order to run unit tests. The existing test suite was run against the implementation and passed successfully. Due to the fact that this project has no front end, the professor asked us to record a video of tests being run to demonstrate functionality, which is linked in the project submission.

Test cases:

* Total score of a review
* Average scores across a review when the maximum score is 0
* Average scores across a review when the maximum score is not 0
* Maximum scores for a response when there are no points available
* Maximum scores for a response standard case
* Volume of review comments
* Concatenating all review comments

= E2313 Reimplement Response Controller =

== Summary of Changes ==

The previous version of response_controller.rb was too long. It included too many functions besides the basic CRUD methods. The goal of E2313 was to reimplement it to follow better coding standards.

* Made method name to follow plural convention not singular convention.
* Moved many functionalities to mixins or helper classes

== Functionality Moved ==

This section covers the functionality that was moved out of the responses controller.

=== Authentication and Authorization ===

There were authentication and authorization methods in the response controller. These were moved to authorization helper.

=== Redirect ===

There was a redirect function that helps redirect by params. It is moved to response helper.

=== Sort Reviews ===

There was functionality to sort reviews. We made a new function named sortReviews to perform this functionality and placed it in the response model

== Singular convention to Plural convention ==

There were some function and classes that followed singular conventions, but were changed to follow plural convention.

[[File:plural.png]]

[[File:authorization_helper.png]]

[[File:macro.png]]

== Reducing code ==

There were multiple method invocations to set parameters (assign_action_parameters, set_content). We used the macro, before_action, so that we reduced the number of calls for these methods.

== Testing ==

1. Response Deletion

- Verify that if the response is enabled for team reviewing, but lock is not existent, proceed to lock response
- Verify that if the response is not team review enabled, proceed to delete the response and redirect the user

2. Response Edit

- Verify preparing already existent response for editing purposes
- Verify creating new response if non-existent for editing purposes

3. Response Update

- Verify submitted response contains the new updated fields upon submission

4. Response New Feedback

- Redirect user to the new feedback page with relevant Response, Participant, and FeedbackResponseMap data
- If a review is not found, redirect user to the root path

5. Response Create

- If Response is found by query parameter, update with additional comments and instantiate answers
- If Response is not found by query parameter, create new Response instance with additional comments and instantiate answers

6. Response Save

- With the found ResponseMap, save with existing query parameters

7. Initialize Answers

- Verify answers are created from a passed-in list of questions

8. Questionnaire from Response Map

- Verify if current map type is ReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is SelfReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is MetareviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is TeammateReviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is FeedbackResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is CourseSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is AssignmentSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is GlobalSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is BookmarkRatingResponseMap, set questionnaire based on if assignment is duty based

9. Assign Action Parameters

- Verify when action is edit, header and next_action are assigned as "Edit" and "update" respectively
- Verify when action is new, header and next_action are assigned as "New" and "create" respectively

10. Setting Response

- Verify response and map instances are set based on the query parameter passed in

11. Toggling permission

- Verify a given response is found and its visibility attribute is toggled to its corresponding opposite value

12. Show Calibration Results for Student

- Verify with the given query parameters: assignment_id, calibration_response_map_id, review_response_map_id, that the assignment, calibration response, review response and questions instances are set correctly

File:Macro.png

2023-03-28T02:34:14Z

Ashon:

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:33:19Z

Ashon: /* Singular convention to Plural convention */

In order to accommodate issues with another team, our team picked up another member and did both projects. The summaries of the projects are combined here to reflect that. Note that the requirements on the original projects are being treated more loosely to account for the additional work.

= E2312 Reimplement Response =

== Summary of Changes ==

The previous version of response.rb was described as "a mess." The goal of E2312 was to reimplement it to follow better coding standards.

* Made method names clearer, many method names were opaque and did not properly convey their functionality. For example, add_table_rows:
[[File:add_table_rows.png]]
* Moved many functionalities to mixins or helper classes to not violate the Single-Responsibility Principle (also many comments with no useful information)
[[File:scores_response.png]]
* Reduced usage of class methods

== Functionality Moved ==

This section covers the functionality that was moved out of the response model.

=== Score Calculation ===

Score calculation is not inherently tied to the idea of a response.
Any object with multiple scores could take advantage of a mixin that provided methods to do calculations on those scores. This created multiple responsibilities for the response object and encouraged non-DRY code.
Functionality for calculating total, average, and maximum scores were all moved to a new Scorable mixin which can be leveraged by other models moving forward.

Previously that functionality was implemented directly on the response class:

[[File:aggregate_score.png]]

Now it exists in a mixin, as demonstrated with this snippet:

[[File:scorable_mixin.png]]

=== Emails ===

The response model provided a method for creating emails. This was moved to a new MailMixin, which can be expanded to provide email functionality to more models in the future. This removed additional responsibilities to help maintain the Single Responsibility principle and helps move email-based code toward a more DRY implementation in the future.

[[File:mail_mixin.png]]

=== Metrics ===

The response model provided a method for getting the volume of review comments on a response. This was moved to a ReviewCommentMixin as it is not necessarily specific to response models. This helps maintain the Single-Responsibility Principle for the response model.

[[File:review_comment.png]]

== Improved Naming ==

Fix instances of bad and opaque naming, like aggregate_question_score(), add_table_row(), and concatenate_all_review_comments() (which does more than the name implies).

== Test Plan ==

Many other parts of the software were stubbed out in the implementation project in order to run unit tests. The existing test suite was run against the implementation and passed successfully. Due to the fact that this project has no front end, the professor asked us to record a video of tests being run to demonstrate functionality, which is linked in the project submission.

Test cases:

* Total score of a review
* Average scores across a review when the maximum score is 0
* Average scores across a review when the maximum score is not 0
* Maximum scores for a response when there are no points available
* Maximum scores for a response standard case
* Volume of review comments
* Concatenating all review comments

= E2313 Reimplement Response Controller =

== Summary of Changes ==

The previous version of response_controller.rb was too long. It included too many functions besides the basic CRUD methods. The goal of E2313 was to reimplement it to follow better coding standards.

* Made method name to follow plural convention not singular convention.
* Moved many functionalities to mixins or helper classes

== Functionality Moved ==

This section covers the functionality that was moved out of the responses controller.

=== Authentication and Authorization ===

There were authentication and authorization methods in the response controller. These were moved to authorization helper.

=== Redirect ===

There was a redirect function that helps redirect by params. It is moved to response helper.

=== Sort Reviews ===

There was functionality to sort reviews. We made a new function named sortReviews to perform this functionality and placed it in the response model

== Singular convention to Plural convention ==

There were some function and classes that followed singular conventions, but were changed to follow plural convention.

[[File:plural.png]]

[[File:authorization_helper.png]]

== Reducing code ==

There were multiple method invocations to set parameters (assign_action_parameters, set_content). We used the macro, before_action, so that we reduced the number of calls for these methods.

== Testing ==

1. Response Deletion

- Verify that if the response is enabled for team reviewing, but lock is not existent, proceed to lock response
- Verify that if the response is not team review enabled, proceed to delete the response and redirect the user

2. Response Edit

- Verify preparing already existent response for editing purposes
- Verify creating new response if non-existent for editing purposes

3. Response Update

- Verify submitted response contains the new updated fields upon submission

4. Response New Feedback

- Redirect user to the new feedback page with relevant Response, Participant, and FeedbackResponseMap data
- If a review is not found, redirect user to the root path

5. Response Create

- If Response is found by query parameter, update with additional comments and instantiate answers
- If Response is not found by query parameter, create new Response instance with additional comments and instantiate answers

6. Response Save

- With the found ResponseMap, save with existing query parameters

7. Initialize Answers

- Verify answers are created from a passed-in list of questions

8. Questionnaire from Response Map

- Verify if current map type is ReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is SelfReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is MetareviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is TeammateReviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is FeedbackResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is CourseSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is AssignmentSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is GlobalSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is BookmarkRatingResponseMap, set questionnaire based on if assignment is duty based

9. Assign Action Parameters

- Verify when action is edit, header and next_action are assigned as "Edit" and "update" respectively
- Verify when action is new, header and next_action are assigned as "New" and "create" respectively

10. Setting Response

- Verify response and map instances are set based on the query parameter passed in

11. Toggling permission

- Verify a given response is found and its visibility attribute is toggled to its corresponding opposite value

12. Show Calibration Results for Student

- Verify with the given query parameters: assignment_id, calibration_response_map_id, review_response_map_id, that the assignment, calibration response, review response and questions instances are set correctly

File:Authorization helper.png

2023-03-28T02:33:10Z

Ashon:

2023-03-28T02:26:09Z

Ashon: /* Singular convention to Plural convention */

In order to accommodate issues with another team, our team picked up another member and did both projects. The summaries of the projects are combined here to reflect that. Note that the requirements on the original projects are being treated more loosely to account for the additional work.

= E2312 Reimplement Response =

== Summary of Changes ==

The previous version of response.rb was described as "a mess." The goal of E2312 was to reimplement it to follow better coding standards.

* Made method names clearer, many method names were opaque and did not properly convey their functionality. For example, add_table_rows:
[[File:add_table_rows.png]]
* Moved many functionalities to mixins or helper classes to not violate the Single-Responsibility Principle (also many comments with no useful information)
[[File:scores_response.png]]
* Reduced usage of class methods

== Functionality Moved ==

This section covers the functionality that was moved out of the response model.

=== Score Calculation ===

Score calculation is not inherently tied to the idea of a response.
Any object with multiple scores could take advantage of a mixin that provided methods to do calculations on those scores. This created multiple responsibilities for the response object and encouraged non-DRY code.
Functionality for calculating total, average, and maximum scores were all moved to a new Scorable mixin which can be leveraged by other models moving forward.

Previously that functionality was implemented directly on the response class:

[[File:aggregate_score.png]]

Now it exists in a mixin, as demonstrated with this snippet:

[[File:scorable_mixin.png]]

=== Emails ===

The response model provided a method for creating emails. This was moved to a new MailMixin, which can be expanded to provide email functionality to more models in the future. This removed additional responsibilities to help maintain the Single Responsibility principle and helps move email-based code toward a more DRY implementation in the future.

[[File:mail_mixin.png]]

=== Metrics ===

The response model provided a method for getting the volume of review comments on a response. This was moved to a ReviewCommentMixin as it is not necessarily specific to response models. This helps maintain the Single-Responsibility Principle for the response model.

[[File:review_comment.png]]

== Improved Naming ==

Fix instances of bad and opaque naming, like aggregate_question_score(), add_table_row(), and concatenate_all_review_comments() (which does more than the name implies).

== Test Plan ==

Many other parts of the software were stubbed out in the implementation project in order to run unit tests. The existing test suite was run against the implementation and passed successfully. Due to the fact that this project has no front end, the professor asked us to record a video of tests being run to demonstrate functionality, which is linked in the project submission.

Test cases:

* Total score of a review
* Average scores across a review when the maximum score is 0
* Average scores across a review when the maximum score is not 0
* Maximum scores for a response when there are no points available
* Maximum scores for a response standard case
* Volume of review comments
* Concatenating all review comments

= E2313 Reimplement Response Controller =

== Summary of Changes ==

The previous version of response_controller.rb was too long. It included too many functions besides the basic CRUD methods. The goal of E2313 was to reimplement it to follow better coding standards.

* Made method name to follow plural convention not singular convention.
* Moved many functionalities to mixins or helper classes

== Functionality Moved ==

This section covers the functionality that was moved out of the responses controller.

=== Authentication and Authorization ===

There were authentication and authorization methods in the response controller. These were moved to authorization helper.

=== Redirect ===

There was a redirect function that helps redirect by params. It is moved to response helper.

=== Sort Reviews ===

There was functionality to sort reviews. We made a new function named sortReviews to perform this functionality and placed it in the response model

== Singular convention to Plural convention ==

There were some function and classes that followed singular conventions, but were changed to follow plural convention.

[[File:/Users/andrewncsu/Desktop/Screenshot 2023-03-27 at 10.23.44 PM.png]]

== Reducing code ==

There were multiple method invocations to set parameters (assign_action_parameters, set_content). We used the macro, before_action, so that we reduced the number of calls for these methods.

== Testing ==

1. Response Deletion

- Verify that if the response is enabled for team reviewing, but lock is not existent, proceed to lock response
- Verify that if the response is not team review enabled, proceed to delete the response and redirect the user

2. Response Edit

- Verify preparing already existent response for editing purposes
- Verify creating new response if non-existent for editing purposes

3. Response Update

- Verify submitted response contains the new updated fields upon submission

4. Response New Feedback

- Redirect user to the new feedback page with relevant Response, Participant, and FeedbackResponseMap data
- If a review is not found, redirect user to the root path

5. Response Create

- If Response is found by query parameter, update with additional comments and instantiate answers
- If Response is not found by query parameter, create new Response instance with additional comments and instantiate answers

6. Response Save

- With the found ResponseMap, save with existing query parameters

7. Initialize Answers

- Verify answers are created from a passed-in list of questions

8. Questionnaire from Response Map

- Verify if current map type is ReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is SelfReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is MetareviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is TeammateReviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is FeedbackResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is CourseSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is AssignmentSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is GlobalSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is BookmarkRatingResponseMap, set questionnaire based on if assignment is duty based

9. Assign Action Parameters

- Verify when action is edit, header and next_action are assigned as "Edit" and "update" respectively
- Verify when action is new, header and next_action are assigned as "New" and "create" respectively

10. Setting Response

- Verify response and map instances are set based on the query parameter passed in

11. Toggling permission

- Verify a given response is found and its visibility attribute is toggled to its corresponding opposite value

12. Show Calibration Results for Student

- Verify with the given query parameters: assignment_id, calibration_response_map_id, review_response_map_id, that the assignment, calibration response, review response and questions instances are set correctly

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:25:25Z

Ashon: /* Singular convention to Plural convention */

In order to accommodate issues with another team, our team picked up another member and did both projects. The summaries of the projects are combined here to reflect that. Note that the requirements on the original projects are being treated more loosely to account for the additional work.

= E2312 Reimplement Response =

== Summary of Changes ==

The previous version of response.rb was described as "a mess." The goal of E2312 was to reimplement it to follow better coding standards.

* Made method names clearer, many method names were opaque and did not properly convey their functionality. For example, add_table_rows:
[[File:add_table_rows.png]]
* Moved many functionalities to mixins or helper classes to not violate the Single-Responsibility Principle (also many comments with no useful information)
[[File:scores_response.png]]
* Reduced usage of class methods

== Functionality Moved ==

This section covers the functionality that was moved out of the response model.

=== Score Calculation ===

Score calculation is not inherently tied to the idea of a response.
Any object with multiple scores could take advantage of a mixin that provided methods to do calculations on those scores. This created multiple responsibilities for the response object and encouraged non-DRY code.
Functionality for calculating total, average, and maximum scores were all moved to a new Scorable mixin which can be leveraged by other models moving forward.

Previously that functionality was implemented directly on the response class:

[[File:aggregate_score.png]]

Now it exists in a mixin, as demonstrated with this snippet:

[[File:scorable_mixin.png]]

=== Emails ===

The response model provided a method for creating emails. This was moved to a new MailMixin, which can be expanded to provide email functionality to more models in the future. This removed additional responsibilities to help maintain the Single Responsibility principle and helps move email-based code toward a more DRY implementation in the future.

[[File:mail_mixin.png]]

=== Metrics ===

The response model provided a method for getting the volume of review comments on a response. This was moved to a ReviewCommentMixin as it is not necessarily specific to response models. This helps maintain the Single-Responsibility Principle for the response model.

[[File:review_comment.png]]

== Improved Naming ==

Fix instances of bad and opaque naming, like aggregate_question_score(), add_table_row(), and concatenate_all_review_comments() (which does more than the name implies).

== Test Plan ==

Many other parts of the software were stubbed out in the implementation project in order to run unit tests. The existing test suite was run against the implementation and passed successfully. Due to the fact that this project has no front end, the professor asked us to record a video of tests being run to demonstrate functionality, which is linked in the project submission.

Test cases:

* Total score of a review
* Average scores across a review when the maximum score is 0
* Average scores across a review when the maximum score is not 0
* Maximum scores for a response when there are no points available
* Maximum scores for a response standard case
* Volume of review comments
* Concatenating all review comments

= E2313 Reimplement Response Controller =

== Summary of Changes ==

The previous version of response_controller.rb was too long. It included too many functions besides the basic CRUD methods. The goal of E2313 was to reimplement it to follow better coding standards.

* Made method name to follow plural convention not singular convention.
* Moved many functionalities to mixins or helper classes

== Functionality Moved ==

This section covers the functionality that was moved out of the responses controller.

=== Authentication and Authorization ===

There were authentication and authorization methods in the response controller. These were moved to authorization helper.

=== Redirect ===

There was a redirect function that helps redirect by params. It is moved to response helper.

=== Sort Reviews ===

There was functionality to sort reviews. We made a new function named sortReviews to perform this functionality and placed it in the response model

== Singular convention to Plural convention ==

There were some function and classes that followed singular conventions, but were changed to follow plural convention.

[[File:/Users/andrewncsu/Desktop/Screenshot 2023-03-27 at 10.23.44 PM.png]]

== Reducing code ==

There were multiple method invocations to set parameters (assign_action_parameters, set_content). We used the macro, before_action, so that we reduced the number of calls for these methods.

== Testing ==

1. Response Deletion

- Verify that if the response is enabled for team reviewing, but lock is not existent, proceed to lock response
- Verify that if the response is not team review enabled, proceed to delete the response and redirect the user

2. Response Edit

- Verify preparing already existent response for editing purposes
- Verify creating new response if non-existent for editing purposes

3. Response Update

- Verify submitted response contains the new updated fields upon submission

4. Response New Feedback

- Redirect user to the new feedback page with relevant Response, Participant, and FeedbackResponseMap data
- If a review is not found, redirect user to the root path

5. Response Create

- If Response is found by query parameter, update with additional comments and instantiate answers
- If Response is not found by query parameter, create new Response instance with additional comments and instantiate answers

6. Response Save

- With the found ResponseMap, save with existing query parameters

7. Initialize Answers

- Verify answers are created from a passed-in list of questions

8. Questionnaire from Response Map

- Verify if current map type is ReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is SelfReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is MetareviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is TeammateReviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is FeedbackResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is CourseSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is AssignmentSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is GlobalSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is BookmarkRatingResponseMap, set questionnaire based on if assignment is duty based

9. Assign Action Parameters

- Verify when action is edit, header and next_action are assigned as "Edit" and "update" respectively
- Verify when action is new, header and next_action are assigned as "New" and "create" respectively

10. Setting Response

- Verify response and map instances are set based on the query parameter passed in

11. Toggling permission

- Verify a given response is found and its visibility attribute is toggled to its corresponding opposite value

12. Show Calibration Results for Student

- Verify with the given query parameters: assignment_id, calibration_response_map_id, review_response_map_id, that the assignment, calibration response, review response and questions instances are set correctly

CSC/ECE 517 Spring 2023 - E2312 + E2313. Reimplement response.rb and responses controller.rb

2023-03-28T02:25:00Z

Ashon: /* Singular convention to Plural convention */

In order to accommodate issues with another team, our team picked up another member and did both projects. The summaries of the projects are combined here to reflect that. Note that the requirements on the original projects are being treated more loosely to account for the additional work.

= E2312 Reimplement Response =

== Summary of Changes ==

The previous version of response.rb was described as "a mess." The goal of E2312 was to reimplement it to follow better coding standards.

* Made method names clearer, many method names were opaque and did not properly convey their functionality. For example, add_table_rows:
[[File:add_table_rows.png]]
* Moved many functionalities to mixins or helper classes to not violate the Single-Responsibility Principle (also many comments with no useful information)
[[File:scores_response.png]]
* Reduced usage of class methods

== Functionality Moved ==

This section covers the functionality that was moved out of the response model.

=== Score Calculation ===

Score calculation is not inherently tied to the idea of a response.
Any object with multiple scores could take advantage of a mixin that provided methods to do calculations on those scores. This created multiple responsibilities for the response object and encouraged non-DRY code.
Functionality for calculating total, average, and maximum scores were all moved to a new Scorable mixin which can be leveraged by other models moving forward.

Previously that functionality was implemented directly on the response class:

[[File:aggregate_score.png]]

Now it exists in a mixin, as demonstrated with this snippet:

[[File:scorable_mixin.png]]

=== Emails ===

The response model provided a method for creating emails. This was moved to a new MailMixin, which can be expanded to provide email functionality to more models in the future. This removed additional responsibilities to help maintain the Single Responsibility principle and helps move email-based code toward a more DRY implementation in the future.

[[File:mail_mixin.png]]

=== Metrics ===

The response model provided a method for getting the volume of review comments on a response. This was moved to a ReviewCommentMixin as it is not necessarily specific to response models. This helps maintain the Single-Responsibility Principle for the response model.

[[File:review_comment.png]]

== Improved Naming ==

Fix instances of bad and opaque naming, like aggregate_question_score(), add_table_row(), and concatenate_all_review_comments() (which does more than the name implies).

== Test Plan ==

Many other parts of the software were stubbed out in the implementation project in order to run unit tests. The existing test suite was run against the implementation and passed successfully. Due to the fact that this project has no front end, the professor asked us to record a video of tests being run to demonstrate functionality, which is linked in the project submission.

Test cases:

* Total score of a review
* Average scores across a review when the maximum score is 0
* Average scores across a review when the maximum score is not 0
* Maximum scores for a response when there are no points available
* Maximum scores for a response standard case
* Volume of review comments
* Concatenating all review comments

= E2313 Reimplement Response Controller =

== Summary of Changes ==

The previous version of response_controller.rb was too long. It included too many functions besides the basic CRUD methods. The goal of E2313 was to reimplement it to follow better coding standards.

* Made method name to follow plural convention not singular convention.
* Moved many functionalities to mixins or helper classes

== Functionality Moved ==

This section covers the functionality that was moved out of the responses controller.

=== Authentication and Authorization ===

There were authentication and authorization methods in the response controller. These were moved to authorization helper.

=== Redirect ===

There was a redirect function that helps redirect by params. It is moved to response helper.

=== Sort Reviews ===

There was functionality to sort reviews. We made a new function named sortReviews to perform this functionality and placed it in the response model

== Singular convention to Plural convention ==

There were some function and classes that followed singular conventions, but were changed to follow plural convention.

/Users/andrewncsu/Desktop/Screenshot 2023-03-27 at 10.23.44 PM.png

== Reducing code ==

There were multiple method invocations to set parameters (assign_action_parameters, set_content). We used the macro, before_action, so that we reduced the number of calls for these methods.

== Testing ==

1. Response Deletion

- Verify that if the response is enabled for team reviewing, but lock is not existent, proceed to lock response
- Verify that if the response is not team review enabled, proceed to delete the response and redirect the user

2. Response Edit

- Verify preparing already existent response for editing purposes
- Verify creating new response if non-existent for editing purposes

3. Response Update

- Verify submitted response contains the new updated fields upon submission

4. Response New Feedback

- Redirect user to the new feedback page with relevant Response, Participant, and FeedbackResponseMap data
- If a review is not found, redirect user to the root path

5. Response Create

- If Response is found by query parameter, update with additional comments and instantiate answers
- If Response is not found by query parameter, create new Response instance with additional comments and instantiate answers

6. Response Save

- With the found ResponseMap, save with existing query parameters

7. Initialize Answers

- Verify answers are created from a passed-in list of questions

8. Questionnaire from Response Map

- Verify if current map type is ReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is SelfReviewResponseMap, set current round and questionnaire accordingly
- Verify if current map type is MetareviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is TeammateReviewResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is FeedbackResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is CourseSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is AssignmentSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is GlobalSurveyResponseMap, set questionnaire based on if assignment is duty based
- Verify if current map type is BookmarkRatingResponseMap, set questionnaire based on if assignment is duty based

9. Assign Action Parameters

- Verify when action is edit, header and next_action are assigned as "Edit" and "update" respectively
- Verify when action is new, header and next_action are assigned as "New" and "create" respectively

10. Setting Response

- Verify response and map instances are set based on the query parameter passed in

11. Toggling permission

- Verify a given response is found and its visibility attribute is toggled to its corresponding opposite value

12. Show Calibration Results for Student

- Verify with the given query parameters: assignment_id, calibration_response_map_id, review_response_map_id, that the assignment, calibration response, review response and questions instances are set correctly