Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2022 - E2228. Refactor JavaScript on Expertiza

2022-04-12T02:33:42Z

Sjanard:

== Problem Statement==
Refactor JavaScript on Expertiza for but not limited to the Assignment View

== Background ==
Expertiza is a software project that uses peer review to produce reusable learning items. It also allows for the uploading of practically any document type, including URLs and wiki pages, as well as team projects.Expertiza’s primary language for managing views is JavaScript. However, these scripts are not well structured and present a large scope of improvement in terms of code quality and optimization.

== Files to be modified ==
* assignments/edit/_due_dates.html.erb
* assignments/edit/_rubrics.html.erb
* assignments/edit/_general.html.erb
* assignments/edit.html.erb -> 76 lines of JS

== What needs to be done ==
* Most JavaScript functions are present as part of erb files. The erb files that use JavaScript but do not use arguments that can be accessed by Ruby code have to be extracted and included as a JavaScript partial.
* For functions that utilize JavaScript and Ruby code, we have two choices
* Refactor the existing methods to ensure that it follows DRY, ensure functions are modular and follow Single Responsibility.
* Use an npm package called erb to inject erb code into JavaScript code.
* Optimize all the code so that they follow DRY principles.
* Documentation for each method and proper indentation is absent. Our aim would be to provide descriptive comments for each method as well as make code readable by properly indentation.
* Introduce the Single Responsibility Principle, which stipulates that a method or function should only be used for one reason and thereby increases code reuse.
* Identify and remove functions do not serve any purpose as well as remove unnecessary documentation/methods that have been commented out.
* Change deprecated JavaScript syntax to ES6 syntax.

== Issues and potential fixes ==

3.

4. Isolate Javascript

For Javascript methods that do not use any erb tags, we isolate them and keep them in a separate file. This is done since we do not need embedded ruby in the Javascript function and the logic can be separated out. Performing this fix makes the code more readable and easier to handle as well as understand.

Fix: As can be seen in the code snippet above, all the javascript functions have been included in the .html.erb file. These can be moved to a separate directory, for instance app/assets/javascript/

CSC/ECE 517 Spring 2022 - E2228. Refactor JavaScript on Expertiza

2022-04-11T01:54:25Z

Sjanard:

== Problem Statement==
Refactor JavaScript on Expertiza for but not limited to the Assignment View

== Background ==
Expertiza is a software project that uses peer review to produce reusable learning items. It also allows for the uploading of practically any document type, including URLs and wiki pages, as well as team projects.Expertiza’s primary language for managing views is JavaScript. However, these scripts are not well structured and present a large scope of improvement in terms of code quality and optimization.

== Issues with existing functionality ==
* assignments/edit/_due_dates.html.erb -> 470 lines of JS.
* assignments/edit/_rubrics.html.erb -> 400 lines of JS.
* assignments/_general.html.erb -> ~200 lines of JS.
* hasTeamsChanged has violated the DRY principle. It adds input fields and handles checkboxes hidden states in other views. Every UI element that depends on hasTeams? checkbox should add a listener in their own view's js file. (Refer assignments/edit/_review_strategy.html.erb line 203 for reference).
* assignments/edit.html.erb -> 76 lines of JS

== What needs to be done ==
* Most JavaScript functions are present as part of erb files. The erb files that use JavaScript but do not use arguments that can be accessed by Ruby code have to be extracted and included as a JavaScript partial.
* For functions that utilize JavaScript and Ruby code, we have two choices
* Refactor the existing methods to ensure that it follows DRY, ensure functions are modular and follow Single Responsibility.
* Use an npm package called erb to inject erb code into JavaScript code.
* Optimize all the code so that they follow DRY principles.
* Documentation for each method and proper indentation is absent. Our aim would be to provide descriptive comments for each method as well as make code readable by properly indentation.
* Introduce the Single Responsibility Principle, which stipulates that a method or function should only be used for one reason and thereby increases code reuse.
* Identify and remove functions do not serve any purpose as well as remove unnecessary documentation/methods that have been commented out.
* Change deprecated JavaScript syntax to ES6 syntax.

CSC/ECE 517 Spring 2022 - E2228. Refactor JavaScript on Expertiza

2022-04-11T01:05:28Z

Sjanard:

== Problem Statement==
Refactor JavaScript on Expertiza for but not limited to the Assignment View

== Background ==
Expertiza is a software project that uses peer review to produce reusable learning items. It also allows for the uploading of practically any document type, including URLs and wiki pages, as well as team projects.Expertiza’s primary language for managing views is JavaScript. However, these scripts are not well structured and present a large scope of improvement in terms of code quality and optimization.

== Issues with existing functionality ==
* assignments/edit/_due_dates.html.erb -> 470 lines of JS.
* assignments/edit/_rubrics.html.erb -> 400 lines of JS.
* assignments/_general.html.erb -> ~200 lines of JS.
* hasTeamsChanged has violated the DRY principle. It adds input fields and handles checkboxes hidden states in other views. Every UI element that depends on hasTeams? checkbox should add a listener in their own view's js file. (Refer assignments/edit/_review_strategy.html.erb line 203 for reference).
* assignments/edit.html.erb -> 76 lines of JS

== What needs to be done ==
* Most JavaScript functions are present as part of erb files. The erb files that use JavaScript but do not use arguments that can be accessed by Ruby code have to be extracted and included as a JavaScript partial.
* For functions that utilize JavaScript and Ruby code, we have two choices
* Refactor the existing methods to ensure that it follows DRY, ensure functions are modular and follow Single Responsibility.
* Use an npm package called erb to inject erb code into JavaScript code.
* Optimize all the code so that they follow DRY principles.
* Documentation for each method and proper indentation is absent. Our aim would be to provide descriptive comments for each method as well as make code readable by properly indentation.
* Introduce the Single Responsibility Principle, which stipulates that a method or function should only be used for one reason and thereby increases code reuse.
* Identify and remove functions do not serve any purpose as well as remove unnecessary documentation/methods that have been commented out.

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-28T03:14:12Z

Sjanard: /* Manual UI Testing */

This wiki page is for the description of changes made under E2225 OSS assignment for Fall 2022, CSC 517.

== Expertiza Background==

Expertiza is an educational web application created and maintained by the joint efforts of the students and the faculty at NCSU. It’s an open source project developed on Ruby on Rails platform and it’s code is available on Github. It allows students to review each other’s work and improve their work upon this feedback.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===
* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Files modified in current project ==

A helper file has been modified for this project namely: 

1. review_mapping_helper.rb 
2. /reports/_feedback_report.html.erb 
3. spec/helpers/review_mapping_helper_spec.rb 

== List of changes ==

We worked on the following work items(WIs) 
WI1 : Refactor get_team_color method to reduce cognitive complexity 
WI2 : Refactor check_submission_state to reduce cognitive complexity 
WI3 : Improved assignment branch condition of method get_awarded_review_score 
WI4 : Refactored review_metrics method to reduce cognitive complexity 
WI5 : Refactored calculate_key_chart_information to reduce complexity 
WI6 : Added top level class documentation and corrected indentation 
WI7 : Updated method names for method name too long issue 

=== Solutions Implemented and Delivered ===

==== 1. Refactoring get_team_color method ====

This method retrieves the team's color according to the state of the review and assignment status

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and utilized the unless statement to make the code ruby friendly.

Initial code:

[[File:Get team color initial.png]]

Refactored code:

[[File:Get_team_color_final.png]]

==== 2. Refactoring check_submission_state method ====

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and used inline if conditions to make the code more concise.

Initial code:

[[File:Css initial.png]]

Refactored code:

[[File:Css final.png]]

==== 3.Refactoring get_awarded_review_score to reduce the Assignment Branch Condition size ====

Assignment Branch Condition size for get_awarded_review_score was too high. Reduced the ABC size to make the method more readily understood, more reusable and more testable.

[[File:Awarded_review_score.png]]

==== 4. Refactoring review_metrics method ====

We utilize the unless statement to return an empty value if there is no review associated with a given team, eliminating the use of if statements in favor of ruby styled code.

Refactored code:

[[File:Review metrics.png]]

==== 5. Refactored calculate_key_chart_information to reduce complexity ====

Used a guard clause instead of wrapping the code inside a conditional expression. Having simplicity, atomic definitions and eager return statements are ways to keep the code base concise.

[[File:Key_chart_info.png]]

==== 6. Top level documentation and corrected indentation ====

We've added top level documentation to describe the functionality of classes such as the ReviewStrategy class, StudentReviewStrategy class and TeamReviewStratregy class. 
Ruby style guidelines dictate that 2 spaces be used instead of tabs. We've performed these changes throughout the document.

==== 7. Method name too long issue ====

Changed the name of the method get_each_review_and_feedback_response_map method to get_each_review_and_feedback and get_certain_review_and_feedback_response_map was changed to get_certain_review_feedback.

== Test Plan ==
=== Manual UI Testing ===
As mentioned previously, the function of the review_mapping_helper file is to ease the responsibilities of the review_mapping_controller. Repetitive tasks such associated with the review controller are performed in this helper file.
The video embedded below provides the UI testing performed on the helper method.

[https://drive.google.com/file/d/1TqEsRK2nyK3DL49P9Lq-g1OZ3S_K5GrF/view Link to UI Test] 

=== RSpec Unit Tests ===
As a result, no functionality in any function has changed; only refactoring has taken place.
All of the refactoring was thoroughly tested using rspec tests.
Run the following command to run the spec file: rspec spec/controllers/review mapping controller spec.rb. No functionality was broken as a result of the refactoring.
Adding additional testcases is out of the question since this is primarily a refactoring project since no additional methods were added.
As we can see from the image below, running spec/helpers/review_mapping_helper_spec.rb command, we pass all test cases

[[File:Screen Shot 2022-03-27 at 10.44.50 PM.png]]

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-28T03:10:16Z

Sjanard: /* RSpec Unit Tests */

This wiki page is for the description of changes made under E2225 OSS assignment for Fall 2022, CSC 517.

== Expertiza Background==

Expertiza is an educational web application created and maintained by the joint efforts of the students and the faculty at NCSU. It’s an open source project developed on Ruby on Rails platform and it’s code is available on Github. It allows students to review each other’s work and improve their work upon this feedback.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===
* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Files modified in current project ==

A helper file has been modified for this project namely: 

1. review_mapping_helper.rb 
2. /reports/_feedback_report.html.erb 
3. spec/helpers/review_mapping_helper_spec.rb 

== List of changes ==

We worked on the following work items(WIs) 
WI1 : Refactor get_team_color method to reduce cognitive complexity 
WI2 : Refactor check_submission_state to reduce cognitive complexity 
WI3 : Improved assignment branch condition of method get_awarded_review_score 
WI4 : Refactored review_metrics method to reduce cognitive complexity 
WI5 : Refactored calculate_key_chart_information to reduce complexity 
WI6 : Added top level class documentation and corrected indentation 
WI7 : Updated method names for method name too long issue 

=== Solutions Implemented and Delivered ===

==== 1. Refactoring get_team_color method ====

This method retrieves the team's color according to the state of the review and assignment status

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and utilized the unless statement to make the code ruby friendly.

Initial code:

[[File:Get team color initial.png]]

Refactored code:

[[File:Get_team_color_final.png]]

==== 2. Refactoring check_submission_state method ====

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and used inline if conditions to make the code more concise.

Initial code:

[[File:Css initial.png]]

Refactored code:

[[File:Css final.png]]

==== 3.Refactoring get_awarded_review_score to reduce the Assignment Branch Condition size ====

Assignment Branch Condition size for get_awarded_review_score was too high. Reduced the ABC size to make the method more readily understood, more reusable and more testable.

[[File:Awarded_review_score.png]]

==== 4. Refactoring review_metrics method ====

We utilize the unless statement to return an empty value if there is no review associated with a given team, eliminating the use of if statements in favor of ruby styled code.

Refactored code:

[[File:Review metrics.png]]

==== 5. Refactored calculate_key_chart_information to reduce complexity ====

Used a guard clause instead of wrapping the code inside a conditional expression. Having simplicity, atomic definitions and eager return statements are ways to keep the code base concise.

[[File:Key_chart_info.png]]

==== 6. Top level documentation and corrected indentation ====

We've added top level documentation to describe the functionality of classes such as the ReviewStrategy class, StudentReviewStrategy class and TeamReviewStratregy class. 
Ruby style guidelines dictate that 2 spaces be used instead of tabs. We've performed these changes throughout the document.

==== 7. Method name too long issue ====

Changed the name of the method get_each_review_and_feedback_response_map method to get_each_review_and_feedback and get_certain_review_and_feedback_response_map was changed to get_certain_review_feedback.

== Test Plan ==
=== Manual UI Testing ===
As mentioned previously, the function of the review_mapping_helper file is to ease the responsibilities of the review_mapping_controller. Repetitive tasks such associated with the review controller are performed in this helper file.
The video embedded below provides the UI testing performed on the helper method.

=== RSpec Unit Tests ===
As a result, no functionality in any function has changed; only refactoring has taken place.
All of the refactoring was thoroughly tested using rspec tests.
Run the following command to run the spec file: rspec spec/controllers/review mapping controller spec.rb. No functionality was broken as a result of the refactoring.
Adding additional testcases is out of the question since this is primarily a refactoring project since no additional methods were added.
As we can see from the image below, running spec/helpers/review_mapping_helper_spec.rb command, we pass all test cases

[[File:Screen Shot 2022-03-27 at 10.44.50 PM.png]]

File:Screen Shot 2022-03-27 at 10.44.50 PM.png

2022-03-28T03:09:58Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-28T03:09:28Z

Sjanard:

This wiki page is for the description of changes made under E2225 OSS assignment for Fall 2022, CSC 517.

== Expertiza Background==

Expertiza is an educational web application created and maintained by the joint efforts of the students and the faculty at NCSU. It’s an open source project developed on Ruby on Rails platform and it’s code is available on Github. It allows students to review each other’s work and improve their work upon this feedback.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===
* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Files modified in current project ==

A helper file has been modified for this project namely: 

1. review_mapping_helper.rb 
2. /reports/_feedback_report.html.erb 
3. spec/helpers/review_mapping_helper_spec.rb 

== List of changes ==

We worked on the following work items(WIs) 
WI1 : Refactor get_team_color method to reduce cognitive complexity 
WI2 : Refactor check_submission_state to reduce cognitive complexity 
WI3 : Improved assignment branch condition of method get_awarded_review_score 
WI4 : Refactored review_metrics method to reduce cognitive complexity 
WI5 : Refactored calculate_key_chart_information to reduce complexity 
WI6 : Added top level class documentation and corrected indentation 
WI7 : Updated method names for method name too long issue 

=== Solutions Implemented and Delivered ===

==== 1. Refactoring get_team_color method ====

This method retrieves the team's color according to the state of the review and assignment status

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and utilized the unless statement to make the code ruby friendly.

Initial code:

[[File:Get team color initial.png]]

Refactored code:

[[File:Get_team_color_final.png]]

==== 2. Refactoring check_submission_state method ====

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and used inline if conditions to make the code more concise.

Initial code:

[[File:Css initial.png]]

Refactored code:

[[File:Css final.png]]

==== 3.Refactoring get_awarded_review_score to reduce the Assignment Branch Condition size ====

Assignment Branch Condition size for get_awarded_review_score was too high. Reduced the ABC size to make the method more readily understood, more reusable and more testable.

[[File:Awarded_review_score.png]]

==== 4. Refactoring review_metrics method ====

We utilize the unless statement to return an empty value if there is no review associated with a given team, eliminating the use of if statements in favor of ruby styled code.

Refactored code:

[[File:Review metrics.png]]

==== 5. Refactored calculate_key_chart_information to reduce complexity ====

Used a guard clause instead of wrapping the code inside a conditional expression. Having simplicity, atomic definitions and eager return statements are ways to keep the code base concise.

[[File:Key_chart_info.png]]

==== 6. Top level documentation and corrected indentation ====

We've added top level documentation to describe the functionality of classes such as the ReviewStrategy class, StudentReviewStrategy class and TeamReviewStratregy class. 
Ruby style guidelines dictate that 2 spaces be used instead of tabs. We've performed these changes throughout the document.

==== 7. Method name too long issue ====

Changed the name of the method get_each_review_and_feedback_response_map method to get_each_review_and_feedback and get_certain_review_and_feedback_response_map was changed to get_certain_review_feedback.

== Test Plan ==
=== Manual UI Testing ===
As mentioned previously, the function of the review_mapping_helper file is to ease the responsibilities of the review_mapping_controller. Repetitive tasks such associated with the review controller are performed in this helper file.
The video embedded below provides the UI testing performed on the helper method.

=== RSpec Unit Tests ===
As a result, no functionality in any function has changed; only refactoring has taken place.
All of the refactoring was thoroughly tested using rspec tests.
Run the following command to run the spec file: rspec spec/controllers/review mapping controller spec.rb. No functionality was broken as a result of the refactoring.
Adding additional testcases is out of the question since this is primarily a refactoring project since no additional methods were added.
As we can see from the image below, running spec/helpers/review_mapping_helper_spec.rb command, we pass all test cases

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-28T01:57:12Z

Sjanard: /* RSpec Unit Tests */

This wiki page is for the description of changes made under E2225 OSS assignment for Fall 2022, CSC 517.

== Expertiza Background==

Expertiza is an educational web application created and maintained by the joint efforts of the students and the faculty at NCSU. It’s an open source project developed on Ruby on Rails platform and it’s code is available on Github. It allows students to review each other’s work and improve their work upon this feedback.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===
* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Files modified in current project ==

A helper file has been modified for this project namely: 

1. review_mapping_helper.rb 
2. /reports/_feedback_report.html.erb 
3. spec/helpers/review_mapping_helper_spec.rb 

== List of changes ==

We worked on the following work items(WIs) 
WI1 : Refactor get_team_color method to reduce cognitive complexity 
WI2 : Refactor check_submission_state to reduce cognitive complexity 
WI3 : Improved assignment branch condition of method get_awarded_review_score 
WI4 : Refactored review_metrics method to reduce cognitive complexity 
WI5 : Refactored calculate_key_chart_information to reduce complexity 
WI6 : Added top level class documentation and corrected indentation 
WI7 : Updated method names for method name too long issue 

=== Solutions Implemented and Delivered ===

==== 1. Refactoring get_team_color method ====

This method retrieves the team's color according to the state of the review and assignment status

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and utilized the unless statement to make the code ruby friendly.

Initial code:

[[File:Get team color initial.png]]

Refactored code:

[[File:Get_team_color_final.png]]

==== 2. Refactoring check_submission_state method ====

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and used inline if conditions to make the code more concise.

Initial code:

[[File:Css initial.png]]

Refactored code:

[[File:Css final.png]]

==== 3.Refactoring get_awarded_review_score to reduce the Assignment Branch Condition size ====

Assignment Branch Condition size for get_awarded_review_score was too high. Reduced the ABC size to make the method more readily understood, more reusable and more testable.

[[File:Awarded_review_score.png]]

==== 4. Refactoring review_metrics method ====

We utilize the unless statement to return an empty value if there is no review associated with a given team, eliminating the use of if statements in favor of ruby styled code.

Refactored code:

[[File:Review metrics.png]]

==== 5. Refactored calculate_key_chart_information to reduce complexity ====

Used a guard clause instead of wrapping the code inside a conditional expression. Having simplicity, atomic definitions and eager return statements are ways to keep the code base concise.

[[File:Key_chart_info.png]]

==== 6. Top level documentation and corrected indentation ====

We've added top level documentation to describe the functionality of classes such as the ReviewStrategy class, StudentReviewStrategy class and TeamReviewStratregy class. 
Ruby style guidelines dictate that 2 spaces be used instead of tabs. We've performed these changes throughout the document.

==== 7. Method name too long issue ====

Changed the name of the method get_each_review_and_feedback_response_map method to get_each_review_and_feedback and get_certain_review_and_feedback_response_map was changed to get_certain_review_feedback.

== Test Plan ==
=== Manual UI Testing ===
As mentioned previously, the function of the review_mapping_helper file is to ease the responsibilities of the review_mapping_controller. Repetitive tasks such associated with the review controller are performed in this helper file.
The video embedded below provides the UI testing performed on the helper method.

=== RSpec Unit Tests ===
As a result, no functionality in any function has changed; only refactoring has taken place.
All of the refactoring was thoroughly tested using rspec tests.
Run the following command to run the spec file: rspec spec/controllers/review mapping controller spec.rb. No functionality was broken as a result of the refactoring.
Adding additional testcases is out of the question since this is primarily a refactoring project since no additional methods were added.

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-28T01:56:51Z

Sjanard:

This wiki page is for the description of changes made under E2225 OSS assignment for Fall 2022, CSC 517.

== Expertiza Background==

Expertiza is an educational web application created and maintained by the joint efforts of the students and the faculty at NCSU. It’s an open source project developed on Ruby on Rails platform and it’s code is available on Github. It allows students to review each other’s work and improve their work upon this feedback.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===
* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Files modified in current project ==

A helper file has been modified for this project namely: 

1. review_mapping_helper.rb 
2. /reports/_feedback_report.html.erb 
3. spec/helpers/review_mapping_helper_spec.rb 

== List of changes ==

We worked on the following work items(WIs) 
WI1 : Refactor get_team_color method to reduce cognitive complexity 
WI2 : Refactor check_submission_state to reduce cognitive complexity 
WI3 : Improved assignment branch condition of method get_awarded_review_score 
WI4 : Refactored review_metrics method to reduce cognitive complexity 
WI5 : Refactored calculate_key_chart_information to reduce complexity 
WI6 : Added top level class documentation and corrected indentation 
WI7 : Updated method names for method name too long issue 

=== Solutions Implemented and Delivered ===

==== 1. Refactoring get_team_color method ====

This method retrieves the team's color according to the state of the review and assignment status

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and utilized the unless statement to make the code ruby friendly.

Initial code:

[[File:Get team color initial.png]]

Refactored code:

[[File:Get_team_color_final.png]]

==== 2. Refactoring check_submission_state method ====

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and used inline if conditions to make the code more concise.

Initial code:

[[File:Css initial.png]]

Refactored code:

[[File:Css final.png]]

==== 3.Refactoring get_awarded_review_score to reduce the Assignment Branch Condition size ====

Assignment Branch Condition size for get_awarded_review_score was too high. Reduced the ABC size to make the method more readily understood, more reusable and more testable.

[[File:Awarded_review_score.png]]

==== 4. Refactoring review_metrics method ====

We utilize the unless statement to return an empty value if there is no review associated with a given team, eliminating the use of if statements in favor of ruby styled code.

Refactored code:

[[File:Review metrics.png]]

==== 5. Refactored calculate_key_chart_information to reduce complexity ====

Used a guard clause instead of wrapping the code inside a conditional expression. Having simplicity, atomic definitions and eager return statements are ways to keep the code base concise.

[[File:Key_chart_info.png]]

==== 6. Top level documentation and corrected indentation ====

We've added top level documentation to describe the functionality of classes such as the ReviewStrategy class, StudentReviewStrategy class and TeamReviewStratregy class. 
Ruby style guidelines dictate that 2 spaces be used instead of tabs. We've performed these changes throughout the document.

==== 7. Method name too long issue ====

Changed the name of the method get_each_review_and_feedback_response_map method to get_each_review_and_feedback and get_certain_review_and_feedback_response_map was changed to get_certain_review_feedback.

== Test Plan ==
=== Manual UI Testing ===
As mentioned previously, the function of the review_mapping_helper file is to ease the responsibilities of the review_mapping_controller. Repetitive tasks such associated with the review controller are performed in this helper file.
The video embedded below provides the UI testing performed on the helper method.

=== RSpec Unit Tests ===
As a result, no functionality in any function has changed; only refactoring has taken place.
All of the refactoring was thoroughly tested using rspec tests.
Run the following command to run the spec file: rspec spec/controllers/review mapping controller spec.rb. No functionality was broken as a result of the refactoring.
Adding additional testcases is out of the question since this is primarily a refactoring project.and no additional methods were added.

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-22T03:43:45Z

Sjanard: /* Scope for future improvement */

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-22T01:33:00Z

Sjanard: /* 7. Method name too long issue */

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-22T01:25:12Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-22T01:16:46Z

Sjanard:

This wiki page is for the description of changes made under E2225 OSS assignment for Fall 2022, CSC 517.

== Expertiza Background==

Expertiza is an educational web application created and maintained by the joint efforts of the students and the faculty at NCSU. It’s an open source project developed on Ruby on Rails platform and it’s code is available on Github. It allows students to review each other’s work and improve their work upon this feedback.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===
* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Files modified in current project ==

A helper file has been modified for this project namely: 

1. review_mapping_helper.rb 

== List of changes ==

We worked on the following work items(WIs) 
WI1 : Refactor get_team_color method to reduce cognitive complexity 
WI2 : Refactor check_submission_state to reduce cognitive complexity 
WI3 : Improved assignment branch condition of method get_awarded_review_score 
WI4 : Refactored review_metrics method to reduce cognitive complexity 
WI5 : Refactored calculate_key_chart_information to reduce complexity 
WI6 : Added top level class documentation and corrected indentation 
WI7 : Updated method names for method name too long issue 

=== Solutions Implemented and Delivered ===

==== 1. Refactoring get_team_color method ====

This method retrieves the team's color according to the state of the review and assignment status

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and utilized the unless statement to make the code ruby friendly.

Initial code:

[[File:Get team color initial.png]]

Refactored code:

[[File:Get_team_color_final.png]]

==== 2. Refactoring check_submission_state method ====

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and used inline if conditions to make the code more concise.

Initial code:

[[File:Css initial.png]]

Refactored code:

[[File:Css final.png]]

==== 3.Refactoring get_awarded_review_score to reduce the Assignment Branch Condition size ====

Assignment Branch Condition size for get_awarded_review_score was too high. Reduced the ABC size to make the method more readily understood, more reusable and more testable.

[[File:Awarded_review_score.png]]

==== 4. Refactoring review_metrics method ====

We utilize the unless statement to return an empty value if there is no review associated with a given team, eliminating the use of if statements in favor of ruby styled code.

Refactored code:

[[File:Review metrics.png]]

==== 5. Refactored calculate_key_chart_information to reduce complexity ====

Used a guard clause instead of wrapping the code inside a conditional expression. Having simplicity, atomic definitions and eager return statements are ways to keep the code base concise.

[[File:Key_chart_info.png]]

==== 6. Top level documentation and corrected indentation ====

We've added top level documentation to describe the functionality of classes such as the ReviewStrategy class, StudentReviewStrategy class and TeamReviewStratregy class. 
Ruby style guidelines dictate that 2 spaces be used instead of tabs. We've performed these changes throughout the document.

== Scope for future improvement ==

1.

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-22T01:13:02Z

Sjanard:

This wiki page is for the description of changes made under E2225 OSS assignment for Fall 2022, CSC 517.

== Expertiza Background==

Expertiza is an educational web application created and maintained by the joint efforts of the students and the faculty at NCSU. It’s an open source project developed on Ruby on Rails platform and it’s code is available on Github. It allows students to review each other’s work and improve their work upon this feedback.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===
* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Files modified in current project ==

A helper file has been modified for this project namely: 

1. review_mapping_helper.rb 

== List of changes ==

We worked on the following work items(WIs) 
WI1 : Refactor get_team_color method to reduce cognitive complexity 
WI2 : Refactor check_submission_state to reduce cognitive complexity 
WI3 : Improved assignment branch condition of method get_awarded_review_score 
WI4 : Refactored review_metrics method to reduce cognitive complexity 
WI5 : Refactored calculate_key_chart_information to reduce complexity 
WI6 : Added top level class documentation and corrected indentation 
WI7 : Updated method names for method name too long issue 

=== Solutions Implemented and Delivered ===

*Refactoring get_team_color method

1. This method retrieves the team's color according to the state of the review and assignment status

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and utilized the unless statement to make the code ruby friendly.

Initial code:

[[File:Get team color initial.png]]

Refactored code:

[[File:Get_team_color_final.png]]

2. Refactoring check_submission_state method

The initial method consisted of an if clause with multiple if-else statements nested inside. 
We refactored the code and used inline if conditions to make the code more concise.

Initial code:

[[File:Css initial.png]]

Refactored code:

[[File:Css final.png]]

3. Refactoring get_awarded_review_score to reduce the Assignment Branch Condition size

Assignment Branch Condition size for get_awarded_review_score was too high. Reduced the ABC size to make the method more readily understood, more reusable and more testable.

[[File:Awarded_review_score.png]]

4. Refactoring review_metrics method

We utilize the unless statement to return an empty value if there is no review associated with a given team, eliminating the use of if statements in favor of ruby styled code.

Refactored code:

[[File:Review metrics.png]]

5. Refactored calculate_key_chart_information to reduce complexity

Used a guard clause instead of wrapping the code inside a conditional expression. Having simplicity, atomic definitions and eager return statements are ways to keep the code base concise.

[[File:Key_chart_info.png]]

6. Top level documentation and corrected indentation

We've added top level documentation to describe the functionality of classes such as the ReviewStrategy class, StudentReviewStrategy class and TeamReviewStratregy class. 
Ruby style guidelines dictate that 2 spaces be used instead of tabs. We've performed these changes throughout the document.

== Scope for future improvement ==

1.

File:Key chart info.png

2022-03-22T01:12:47Z

Sjanard:

File:Awarded review score.png

2022-03-22T01:07:36Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T22:12:28Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T22:11:46Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T22:05:25Z

Sjanard:

File:Review metrics.png

2022-03-21T22:04:42Z

Sjanard: Sjanard uploaded a new version of File:Review metrics.png

File:Review metrics.png

2022-03-21T22:03:25Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T21:44:15Z

Sjanard:

File:Css final.png

2022-03-21T21:42:25Z

Sjanard:

File:Css initial.png

2022-03-21T21:41:35Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T21:17:05Z

Sjanard:

File:Get team color final.png

2022-03-21T21:16:38Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T21:16:21Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T21:13:25Z

Sjanard:

File:Get team color initial.png

2022-03-21T21:12:30Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T21:10:36Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T20:42:51Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2225: Refactor review mapping helper.rb

2022-03-21T20:22:40Z

Sjanard: Created page with "This wiki page is for the description of changes made under E2225 OSS assignment for Fall 2022, CSC 517. == Expertiza Background== Expertiza is an educational web applicatio..."

CSC/ECE 517 Spring 2022

2022-03-21T20:13:21Z

Sjanard:

[[Link title]]== OSS Projects ==

* [[CSC/ECE 517 Spring 2022 - E2203: Adding tests for courses_controller, eula_controller]]
* [[CSC/ECE 517 Spring 2022 - E2204: Adding tests for markup_styles_controller, lock_controller]]
* [[CSC/ECE 517 Spring 2022 - E2203: Testing for submission_records_controller, profile_controller]]
* [[CSC/ECE 517 Spring 2022 - E2218: Refactor response_controller]]
* [[CSC/ECE 517 Spring 2022 - E2217: Refactor questionnaires_controller]]
* [[CSC/ECE 517 Spring 2022 - E2216: Refactor late_policies_controller]]
* [[CSC/ECE 517 Spring 2022 - E2215: Refactor student_quizzes_controller]]
* [[CSC/ECE 517 Spring 2022 - E2214: Refactor teams_controller]]
* [[CSC/ECE 517 Spring 2022 - E2219: Improve assessment360_controller.rb]]
* [[CSC/ECE 517 Spring 2022 - E2211: Testing for summary_helper]]
* [[CSC/ECE 517 Spring 2022 - E2225: Refactor review_mapping_helper.rb]]
* [[CSC/ECE 517 Spring 2022 - E2221: Refactor submitted content controller.rb]]
* [[CSC/ECE 517 Spring 2022 - E2206: Testing for users_controller]]
* [[CSC/ECE 517 Spring 2022 - E2205: Testing for participants_controller, versions_controller]]
* [[CSC/ECE 517 Spring 2022 - E2212: Testing for hamer.rb]]
* [[CSC/ECE 517 Spring 2022 - S2200: Refactoring evaluation of SQL queries (Java/JUnit)]]
* [[CSC/ECE 517 Spring 2022 - S2222: Refactor impersonate_controller]]
* [[CSC/ECE 517 Spring 2022 - E2202- Testing for badges_controller, publishing_controller]]
*[[CSC/ECE 517 Spring 2022 - E2220: Refactor reputation_web_service_controller]]
* [[CSC/ECE 517 Spring 2022 - E2224: Refactor review_mapping_controller]]
* [[CSC/ECE 517 Spring 2022 - E2209: Testing for analytic helper.rb, join team requests helper.rb]]

== Final Projects ==

CSC/ECE 517 Spring 2022 - E2214: Refactor review mapping helper.rb

2022-03-21T20:11:27Z

Sjanard:

== About Expertiza ==

[http://expertiza.ncsu.edu/ Expertiza] is the software benefits for both instructors and students by supporting various types of submissions and providing reusable objects for peer review. It is an open-source project based on [http://rubyonrails.org/ Ruby on Rails] framework. It allows the instructors not only to create and customize new or existing assignments but also to create a list of topics the students can sign up for. Students can form teams to work on various projects and assignments. Expertiza also lets students peer-review other students' submissions, enabling them to work together to improve others' learning experiences.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===

* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Description about project ==
This page is a description of Expertiza OSS project E2225 is refactoring review_mapping_helper.rb. The work that we have done aims to reduce the size of individual helper methods and attempt to write cleaner code. We have tried our best to write code that is easily readable, concise and not too involved.

=== Files Involved ===

* review_mapping_helper.rb

==Code modifications==

1. Refactored get_team_color method
The functions retrieves the color reflecting the state of the team's review and assignment submission status.
Current code:
<pre>
def get_team_color(response_map)
# Storing redundantly computed value in a variable
assignment_created = @assignment.created_at
# Storing redundantly computed value in a variable
assignment_due_dates = DueDate.where(parent_id: response_map.reviewed_object_id)
# Returning colour based on conditions
if Response.exists?(map_id: response_map.id)
if !response_map.try(:reviewer).try(:review_grade).nil?
'brown'
elsif response_for_each_round?(response_map)
'blue'
else
obtain_team_color(response_map, assignment_created, assignment_due_dates)
end
else
'red'
end
end
</pre>
Modifications:
<pre>
def get_team_color(response_map)
# Storing redundantly computed value in a variable
assignment_created = @assignment.created_at
# Storing redundantly computed value in a variable
assignment_due_dates = DueDate.where(parent_id: response_map.reviewed_object_id)
# Returning colour based on conditions
return 'red' unless Response.exists?(map_id: response_map.id)

if !response_map.try(:reviewer).try(:review_grade).nil?
'brown'
elsif response_for_each_round?(response_map)
'blue'
else
obtain_team_color(response_map, assignment_created, assignment_due_dates)
end
end

</pre>

2. Refactor check_submission_state method
Checks the status of the submission of an assignment or deliverable within each round and assigns the color for the team

Current code:
<pre>
def check_submission_state(response_map, assignment_created, assignment_due_dates, round, color)
if submitted_within_round?(round, response_map, assignment_created, assignment_due_dates)
color.push 'purple'
else
link = submitted_hyperlink(round, response_map, assignment_created, assignment_due_dates)
if link.nil? || (link !~ %r{https*:\/\/wiki(.*)}) # can be extended for github links in future
color.push 'green'
else
link_updated_at = get_link_updated_at(link)
color.push link_updated_since_last?(round, assignment_due_dates, link_updated_at) ? 'purple' : 'green'
end
end
end
</pre>

Modifications:
<pre>
def check_submission_state(response_map, assignment_created, assignment_due_dates, round, color
return color.push 'purple' if submitted_within_round?(round, response_map, assignment_created, assignment_due_dates)

link = submitted_hyperlink(round, response_map, assignment_created, assignment_due_dates)
return color.push 'green' if link.nil? || (link !~ %r{https*:\/\/wiki(.*)})

link_updated_at = get_link_updated_at(link)
color.push link_updated_since_last?(round, assignment_due_dates, link_updated_at) ? 'purple' : 'green'
end
</pre>

==GitHub links==

Link to Expertiza repository: [https://github.com/expertiza/expertiza here]

Link to the forked repository: [https://github.com/amundra02/expertiza here]

CSC/ECE 517 Spring 2022 - E2214: Refactor review mapping helper.rb

2022-03-21T02:56:52Z

Sjanard:

== About Expertiza ==

[http://expertiza.ncsu.edu/ Expertiza] is the software benefits for both instructors and students by supporting various types of submissions and providing reusable objects for peer review. It is an open-source project based on [http://rubyonrails.org/ Ruby on Rails] framework. It allows the instructors not only to create and customize new or existing assignments but also to create a list of topics the students can sign up for. Students can form teams to work on various projects and assignments. Expertiza also lets students peer-review other students' submissions, enabling them to work together to improve others' learning experiences.

== Background ==
A helper method in Ruby performs certain repetitive tasks across multiple classes or a singular class, so that code is not reused and redundancy is reduced. The review_mapping_helper.rb file is primarily used to perform routine tasks with reviews. Tasks such as returning the user's name instead of the team name when there is a single person in the team, checking whether the work has been submitted within the given round and sorting the reviewers by average number of reviews in each round. Each of these functions' visibility is dependent on the type of user.

=== Team Members ===

* Ankur Mundra (amundra@ncsu.edu)
* Shruti Magai (smagai@ncsu.edu)
* Sudharsan Janardhanan (sjanard@ncsu.edu)

== Description about project ==
This page is a description of Expertiza OSS project <Enter Number> is refactoring review_mapping_helper.rb. The work that we have done aims to reduce the size of individual helper methods and attempt to write cleaner code. We have tried our best to write code that is easily readable, concise and not too involved.

=== Files Involved ===

* review_mapping_helper.rb

==Code modifications==

1. Refactored get_team_color method
The functions retrieves the color reflecting the state of the team's review and assignment submission status.
Current code:
<pre>
def get_team_color(response_map)
# Storing redundantly computed value in a variable
assignment_created = @assignment.created_at
# Storing redundantly computed value in a variable
assignment_due_dates = DueDate.where(parent_id: response_map.reviewed_object_id)
# Returning colour based on conditions
if Response.exists?(map_id: response_map.id)
if !response_map.try(:reviewer).try(:review_grade).nil?
'brown'
elsif response_for_each_round?(response_map)
'blue'
else
obtain_team_color(response_map, assignment_created, assignment_due_dates)
end
else
'red'
end
end
</pre>
Modifications:
<pre>
def get_team_color(response_map)
# Storing redundantly computed value in a variable
assignment_created = @assignment.created_at
# Storing redundantly computed value in a variable
assignment_due_dates = DueDate.where(parent_id: response_map.reviewed_object_id)
# Returning colour based on conditions
return 'red' unless Response.exists?(map_id: response_map.id)

if !response_map.try(:reviewer).try(:review_grade).nil?
'brown'
elsif response_for_each_round?(response_map)
'blue'
else
obtain_team_color(response_map, assignment_created, assignment_due_dates)
end
end

</pre>

2. Refactor check_submission_state method
Checks the status of the submission of an assignment or deliverable within each round and assigns the color for the team

Current code:
<pre>
def check_submission_state(response_map, assignment_created, assignment_due_dates, round, color)
if submitted_within_round?(round, response_map, assignment_created, assignment_due_dates)
color.push 'purple'
else
link = submitted_hyperlink(round, response_map, assignment_created, assignment_due_dates)
if link.nil? || (link !~ %r{https*:\/\/wiki(.*)}) # can be extended for github links in future
color.push 'green'
else
link_updated_at = get_link_updated_at(link)
color.push link_updated_since_last?(round, assignment_due_dates, link_updated_at) ? 'purple' : 'green'
end
end
end
</pre>

Modifications:
<pre>
def check_submission_state(response_map, assignment_created, assignment_due_dates, round, color
return color.push 'purple' if submitted_within_round?(round, response_map, assignment_created, assignment_due_dates)

link = submitted_hyperlink(round, response_map, assignment_created, assignment_due_dates)
return color.push 'green' if link.nil? || (link !~ %r{https*:\/\/wiki(.*)})

link_updated_at = get_link_updated_at(link)
color.push link_updated_since_last?(round, assignment_due_dates, link_updated_at) ? 'purple' : 'green'
end
</pre>

==GitHub links==

Link to Expertiza repository: [https://github.com/expertiza/expertiza here]

Link to the forked repository: [https://github.com/amundra02/expertiza here]

CSC/ECE 517 Spring 2022 - E2214: Refactor review mapping helper.rb

2022-03-21T02:26:10Z

Sjanard: /* Team Members */

CSC/ECE 517 Spring 2022 - E2214: Refactor review mapping helper.rb

2022-03-21T02:24:23Z

Sjanard:

CSC/ECE 517 Spring 2022 - E2214: Refactor review mapping helper.rb

2022-03-21T02:00:44Z

Sjanard: Created page with "== About Expertiza== [http://expertiza.ncsu.edu/ Expertiza] is the software benefits for both instructors and students by supporting various types of submissions and providin..."

CSC/ECE 517 Spring 2022

2022-03-21T01:26:10Z

Sjanard:

== OSS Projects ==

* [[CSC/ECE 517 Spring 2022 - E2203: Adding tests for courses_controller, eula_controller]]
* [[CSC/ECE 517 Spring 2022 - E2204: Adding tests for markup_styles_controller, lock_controller]]
* [[CSC/ECE 517 Spring 2022 - E2218: Refactor response_controller]]
* [[CSC/ECE 517 Spring 2022 - E2217: Refactor questionnaires_controller]]
* [[CSC/ECE 517 Spring 2022 - E2216: Refactor late_policies_controller]]
* [[CSC/ECE 517 Spring 2022 - E2215: Refactor student_quizzes_controller]]
* [[CSC/ECE 517 Spring 2022 - E2214: Refactor teams_controller]]
* [[CSC/ECE 517 Spring 2022 - E2219: Improve assessment360_controller.rb]]
* [[CSC/ECE 517 Spring 2022 - E2211: Testing for summary_helper]]
* [[CSC/ECE 517 Spring 2022 - E2214: Refactor review_mapping_helper.rb]]

== Final Projects ==