Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-26T22:51:03Z

Jfwang2:

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

== Changes Made ==
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default review view from displaying analysis for each comment to summarized analysis for all comments
** Do not include comment text in analysis view
** Focus on sentiment_score, suggestions, suggestions_chances returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* Evaluate how much time this API is taking and, if possible, work a way out to improve it.

=== Files that we changed ===
* '''app/views/response/response.html.erb''' - Refactored and reworked JS methods for the autosave and form submits, added a new hidden button to the response form
* '''app/controllers/response_controller.rb''' - Refactored and reworked methods for the autosave and form submits, added an API method to pass to view
* app/helpers/review_mapping_helper.rb - Adjusted the bar thickness according to desired specifications
* config/routes.rb - Added another route to support the new review confirmation page listed below

=== New files we added ===
* '''app/models/metric.rb''' - New ActiveRecord model added to act as a template for future API usage
* '''db/migrate/20190425194052_create_metrics.rb''' - New table added for permanent storage of the Metric class
* '''app/views/response/show_confirmation_page.erb - The new page added for review confirmation
* '''test/fixtures/metrics.yml''' - In support of the new ActiveRecord model called Metric
* '''test/models/metric_test.rb''' - In support of the new ActiveRecord model called Metric
* '''app/assets/images/lightbulb.png''' - Lightbulb picture for the new review confirmation page
* '''app/assets/images/music_note.png''' - A music note picture for the new review confirmation page

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

=== Confirmation Page View ===

=====Student View=====
The program flow is as follows:

# After the reviewer has filled out their review, they have 2 choices: See an analysis of their review or Save the review.
# The reviewer selects to view their analysis by clicking on "Confirm Submission" button
# The program directs the reviewer to the new confirmation page which displays an analysis of their review.
# The reviewer has 2 options in the confirmation page: Submit the review or go back and modify their review.
# If the reviewer decides to Submit their review, the program directs them back to where they started (Create or edit review).

The image below shows the above steps in a visual depiction.
[[File:program_flow.png]]

==== Detailed Popup Information ====
Below we showcase the available information from the API if a reviewer is curious to find more details

[[File:review_response_w_popup_1.png]]
[[File:review_response_w_popup_2.png]]
[[File:review_response_w_popup_3.png]]

==== Conditional Formatting ====
To make the interface more user-friendly, we used conditional formatting to color our text. For the suggestions metrics, anything >50% means suggestions are present while anything <50% means suggestions are absent. Our conditional formatting is set so "Yes (>50%)" is green, 50% is yellow, and "No (<50%)" is red. The formatting is the same for the class average of suggestions metrics.

For tone, there are three options in the API: positive, neutral, and negative. We created conditional formatting in our view file so positive is green text, neutral is yellow text, and negative is red text.

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-15T21:01:08Z

Jfwang2:

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default review view from displaying analysis for each comment to summarized analysis for all comments
** Do not include comment text in analysis view
** Focus on sentiment_score, suggestions, suggestions_chances returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* Evaluate how much time this API is taking and, if possible, work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Production View=====

In the production server, there will be an option at the top of the page to turn on debug mode.
[[File:Debugmode checked.png]]

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews. We are still choosing to omit the "text" item returned in the JSON since it is redundant to display the comment again. Debug mode will be displayed to the right of each review comment.
[[File:Debugmode on.png]]

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-12T20:14:47Z

Jfwang2: /* Non-student View */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default review view from displaying analysis for each comment to summarized analysis for all comments
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* Evaluate how much time this API is taking and, if possible, work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Production View=====

In the production server, there will be an option at the top of the page to turn on debug mode.
[[File:Debugmode checked.png]]

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews. We are still choosing to omit the "text" item returned in the JSON since it is redundant to display the comment again. Debug mode will be displayed to the right of each review comment.
[[File:Debugmode on.png]]

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-12T20:07:14Z

Jfwang2: /* Proposed changes */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default review view from displaying analysis for each comment to summarized analysis for all comments
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* Evaluate how much time this API is taking and, if possible, work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View=====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.
[[File:Debugmode checked.png]]

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews. We are still choosing to omit the "text" item returned in the JSON since it is redundant to display the comment again. Debug mode will be displayed to the right of each review comment.
[[File:Debugmode on.png]]

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-12T20:06:11Z

Jfwang2: /* Proposed changes */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default review view from displaying analysis for each comment to summarized analysis for all comments
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View=====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.
[[File:Debugmode checked.png]]

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews. We are still choosing to omit the "text" item returned in the JSON since it is redundant to display the comment again. Debug mode will be displayed to the right of each review comment.
[[File:Debugmode on.png]]

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

File:Debugmode checked.png

2019-04-12T00:37:50Z

Jfwang2: uploaded a new version of "File:Debugmode checked.png"

File:Debugmode checked.png

2019-04-12T00:37:38Z

Jfwang2: uploaded a new version of "File:Debugmode checked.png": Reverted to version as of 22:14, 11 April 2019

File:Debugmode on.png

2019-04-12T00:34:50Z

Jfwang2: uploaded a new version of "File:Debugmode on.png"

File:Debugmode checked.png

2019-04-12T00:33:50Z

Jfwang2: uploaded a new version of "File:Debugmode checked.png"

File:Debugmode checked.png

2019-04-12T00:33:29Z

Jfwang2: uploaded a new version of "File:Debugmode checked.png": Reverted to version as of 00:32, 12 April 2019

File:Debugmode checked.png

2019-04-12T00:33:04Z

Jfwang2: uploaded a new version of "File:Debugmode checked.png"

File:Debugmode checked.png

2019-04-12T00:32:29Z

Jfwang2: uploaded a new version of "File:Debugmode checked.png"

File:Debugmode on.png

2019-04-12T00:31:18Z

Jfwang2: uploaded a new version of "File:Debugmode on.png"

File:Debugmode on.png

2019-04-12T00:30:39Z

Jfwang2: uploaded a new version of "File:Debugmode on.png"

File:Debugmode checked.png

2019-04-12T00:29:41Z

Jfwang2: uploaded a new version of "File:Debugmode checked.png"

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-11T22:22:35Z

Jfwang2: /* Non-student View */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default view from displaying analysis for each review to summarized analysis for all reviews
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View=====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.
[[File:Debugmode checked.png]]

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews. We are still choosing to omit the "text" item returned in the JSON since it is redundant to display the comment again. Debug mode will be displayed to the right of each review comment.
[[File:Debugmode on.png]]

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-11T22:17:59Z

Jfwang2: /* Response Controller */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default view from displaying analysis for each review to summarized analysis for all reviews
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View=====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.
[[File:Debugmode checked.png]]

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews. We are still choosing to omit the "text" item returned in the JSON since it is redundant to display the comment again.
[[File:Debugmode on.png]]

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-11T22:17:03Z

Jfwang2: /* Response Controller */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default view from displaying analysis for each review to summarized analysis for all reviews
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png|400px]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View=====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.
[[File:Debugmode checked.png]]

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews. We are still choosing to omit the "text" item returned in the JSON since it is redundant to display the comment again.
[[File:Debugmode on.png]]

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-11T22:15:46Z

Jfwang2: /* Non-student View */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default view from displaying analysis for each review to summarized analysis for all reviews
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View=====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.
[[File:Debugmode checked.png]]

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews. We are still choosing to omit the "text" item returned in the JSON since it is redundant to display the comment again.
[[File:Debugmode on.png]]

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

File:Debugmode on.png

2019-04-11T22:15:17Z

Jfwang2:

File:Debugmode checked.png

2019-04-11T22:14:39Z

Jfwang2:

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-11T21:57:58Z

Jfwang2: /* Non-student View */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default view from displaying analysis for each review to summarized analysis for all reviews
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View=====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.

In debug mode, all information returned from the API call will be displayed beside each review instead of only averaging the essential metrics for all reviews.

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-11T21:55:55Z

Jfwang2: /* =Non-student View */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default view from displaying analysis for each review to summarized analysis for all reviews
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View=====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-11T21:55:33Z

Jfwang2: /* Anticipated View */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default view from displaying analysis for each review to summarized analysis for all reviews
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

=====Student View=====
[[File:y.png]]

The student will be given a summary of the feedback in a colorful format. The student will not see all the fields of the JSON and only the necessary text fields, whereas the previous pull request enabled the student to see all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and this will be available to non-students (admins, instructors).

=====Non-student View====

The default view for non-students will match the student view. However, there will be an option at the top of the page to turn on debug mode.

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-11T21:53:04Z

Jfwang2:

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project plan==
===Problem statement===
Peer-review systems like Expertiza utilize a lot of students’ input to determine each other’s performance. At the same time, we hope students learn from the reviews they receive to improve their own performance. In order to make this happen, we would like to have everyone give quality reviews instead of generic ones. Currently we have a few classifiers that can detect useful features of review comments, such as how many suggestions they contain. The suggestion-detection algorithm has been coded as a web service, and other detection algorithms will be so coded in the future.

===How it will work===

In order to make the API call, the response_controller.rb will be responsible for sending a JSON input to the web service. The input will contain the review comment submitted by the user in the following format:

Below is a sample input
Sample Input:
{
"reviews":[{
"text":"review text here",
"metrics":["problem","suggestion","sentiment"]
},{
"text":"another review here",
"metrics":["problem"]
},{
"text":"more text, maybe a large para or whatever you like",
"metrics":["sentiment", "suggestion"]
},{
...
}]
}

Once the request is send, we expect the output to be in the following format:

Sample Output: (as 'suggestion' and 'volume' as you might expect)
{
"metrics":[{
"suggestion":{
"suggestions_chances":30,
"suggestions":"absent"
},
"volume":{
"total_volume":10,
"volume_without_stopwords":3
}
},{
...
},{
...
}]
}

The output (which is a JSON) will be parsed and the suggestion metrics such as the tone and presence of suggestion will be extracted so the user will be able to view a summarized result of how well their review comments were. In addition, an average score will be computed based on the scores they received for each comment section, and the result will be presented in a colorful format to the user after they hit the submit button.

===Previous work===
[https://github.com/expertiza/expertiza/pull/1308 Fall 2018 pull request]
* They had a functional suggestion detection API call that successfully communicated with the PeerLogic Server and retrieved the output.
* They included their API call in response.html.erb using JavaScript.
* They were able to display the output for each review beside the review. They displayed all of the information returned from the endpoint, which can look clunky.
* Since the code is added in the views, they performed manual testing in the views.

More information about the suggestion detection service can be found at https://www.peerlogic.org

[[File:Prev.png]]

=== Flowchart to Describe Plan of Action ===

[[FIle:x.png]]

File(s) involved in making API Call: response_controller.rb
FIle(s) involved in displaying the received output: response.html.erb

===Proposed changes===
* Move API calls of suggestion-detection algorithm from view to response_controller.rb
* Change default view from displaying analysis for each review to summarized analysis for all reviews
** Do not include comment text in analysis view
** Focus on sentiment_score, sentiment_tone, and suggestions metrics returned from API
* Include displaying analysis for each review as a "debug" option
* Ensure that CORS does not need to be enabled for API call to work
* Write unit tests for our method(s) in response_controller.rb
* Fix grammar issues in response.html.erb
* evaluate how much time this API is taking and if possible work a way out to improve it.

==== Response Controller ====
Lines 359 and 360 are where we will retrieve the input from each review comment found in the form.
* The '''Answer''' model represents the review provided by the reviewer.
* On line 360, answer: v[:score] is the review comment from a given textarea HTML element
* params[:responses] stores the aggregate review data provided by the user

[[File:create_answers.png]]

==== Anticipated View ====

[[File:y.png]]

The user will be given a summary of the feedback in a colorful format. The user will not see all the fields of the JSON and only the necessary text fields, whereas currently the user sees all the fields in the output from the API call. We expect to make the detailed view optional so that it can be used for debug purposes, and not be seen in the production server.

===Files that will change===
* '''app/views/response/response.html.erb''': Fix grammar issues, generate view with metrics
* '''app/controllers/response_controller.rb''': Call API here to pass to view

==Testing plan==
There are two aspects to our test plan: Controller and View testing.

=== Controller Tests ===
We will...
* rely on Travis CI automated responses to verify all changes made will not break the system
* ensure that our code coverage does not decrease as a result of our modifications by looking at coveralls messages
* modify Rspec response_controller_spec.rb to reflect the new method(s) added to response_controller.rb
* record and upload a short video verifying our Rspec tests pass

=== View Tests ===
We will...
* use manual testing on response.html.erb to verify the Review page outputs the correct message
* provide sample inputs and show expected outputs using screenshots

==Links to our work==
* [https://github.com/pratikkumar-jain/expertiza/tree/beta Our repository]
* [https://github.com/expertiza/expertiza/pull/1427 Pull request]

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-09T19:35:16Z

Jfwang2: /* Our work */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-09T19:34:59Z

Jfwang2:

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-09T19:34:14Z

Jfwang2:

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-09T19:33:54Z

Jfwang2: /* Task */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T17:27:57Z

Jfwang2: /* Our work */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T17:07:17Z

Jfwang2:

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T16:46:04Z

Jfwang2: /* Previous work */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T16:42:06Z

Jfwang2: /* Proposed changes */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T16:40:10Z

Jfwang2: /* Previous work */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T16:37:41Z

Jfwang2: /* Proposed changes */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T16:35:34Z

Jfwang2: /* Proposed changes */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T16:33:23Z

Jfwang2: /* Project */

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T16:32:54Z

Jfwang2: /* Proposed changes */

==Introduction==
=== Team ===
Dr. Gehringer (mentor)
* Sushan Basnet (sbasnet2)
* Jasmine Wang (jfwang2)
* Bill Mwaniki (bnmwanik)
* Pratik Kumar Kundanmal Jain (pjain22)

==Project==
===Task===
====Problem statement====
====Proposed changes====
* Move API calls of suggestion-detection algorithm from view to response_controller.rb

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-07T16:27:33Z

Jfwang2:

CSC/ECE 517 Spring 2019 - Project E1937. Integrate suggestion detection algorithm.rb

2019-04-05T18:26:47Z

Jfwang2: Created page with "To be updated"

To be updated

CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb

2019-03-31T15:02:56Z

Jfwang2: /* Test Outline/Plan */

==Introduction==
=== Background ===
====Expertiza====
[http://expertiza.ncsu.edu/ Expertiza] is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. (https://github.com/expertiza/expertiza)

====RSpec====
[http://rspec.info/ RSpec] is a 'Domain Specific Language' (DSL) testing tool written in Ruby to test Ruby code. It is a behavior-driven development (BDD) framework which is extensively used in the production applications. The basic idea behind this concept is that of Test Driven Development (TDD) where the tests are written first and the development is based on writing just enough code that will fulfill those tests followed by refactoring. It contains its own mocking framework that is fully integrated into the framework based upon JMock. The simplicity in the RSpec syntax makes it one of the popular testing tools for Ruby applications. The RSpec tool can be used by installing the rspec gem which consists of 3 other gems namely rspec-core, rspec-expectation and rspec-mock. (https://en.wikipedia.org/wiki/RSpec)

===Team===
Zhewei Hu (zhu6) (mentor)
*Jasmine Wang (jfwang2)
*Louis Le (lle3)

==Project==
===Task===
====Problem statement====
There are few tests for assessment360_controller.rb. We had to test the following functions:

* action_allowed
* all_students_all_reviews
* course_student_grade_summary
* populate_hash_for_all_students_all_reviews(assignment,course_participant,reviews,hash_per_stu,overall_review_grade_hash,overall_review_count_hash, review_info_per_stu)
* find_peer_review_score(user_id, assignment_id)
* format_topic(topic)
* format_score(score)

====Overall tasks====
*Write RSpec integration tests to make the statement coverage above 90%.
*Cover as many edge cases as you can.
*Achieve as high branch coverage as you can.
====Our work====
The code we created can be found below. We have also linked the video of our tests running with coverage to showcase the work we have done.
*[https://github.com/expertiza/expertiza/pull/1366 Pull request]
*[https://github.com/jasminewang0/expertiza/tree/beta Our repository on beta branch]
*[https://drive.google.com/file/d/1cNKmslDQGbv4qA62l6Qz3_Akg2BeBSyz/view?usp=sharing Video of tests running]

With the goal of getting at least 90% coverage, our tests got about 97.94%. The way we split up the work by having Jasmine take care of the function: all_students_all reviews while Louis took care of course_student_grade_summary. This helped with potential merge conflicts since both these functions are the biggest of the file and working on them would allow both to make progress at the same time.

====Files====
The following files were the ones either edited or used as aid.
* [https://github.com/expertiza/expertiza/blob/master/app/controllers/assessment360_controller.rb ./app/controllers/assessment360_controller.rb]
* File being tested. (Goal is at least 90%)
* [https://github.com/expertiza/expertiza/blob/master/spec/controllers/assessment360_controller_spec.rb ./spec/controllers/assessment360_controller_spec.rb]
* Test file using RSpec.
* [https://github.com/expertiza/expertiza/blob/master/spec/factories/factories.rb ./spec/factories/factories.rb]
* Super useful file that aided in mocking variable

===Running Tests===
In order to run the integration test, run the following command via terminal:
<pre>
rspec ./spec/controller/assessment360_controller.rb
</pre>

===Test Outline/Plan===
Below shows the outline of what our test look like:

'''assessment360controller'''
#all_students_all_reviews
when it redirects to back and flashes error as there are no participants
when it has participants, next assignment participants does not exist and avoid divide by zero
when it has participants, next assignment participant exists, but there are reviews

#course_student_grade_summary
when course does not have participants
when method is called
when it redirects back and flashes error as there are no participants
when it has participants, next assignment participant does not exist
when it has participants, next assignment participant exist, but no team id exists

CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb

2019-03-31T15:02:40Z

Jfwang2: /* Test Outline/Plan */

CSC/ECE 517 Spring 2019

2019-03-26T15:04:59Z

Jfwang2:

*[[CSC/ECE 517 Spring 2019 - Project E1905. Refactor questionnaires_controller.rb]]
*[[CSC/ECE 517 Spring 2019 - Project E1916. Fix Code Climate issues in controllers with names beginning with A through N]]
*[[CSC/ECE 517 Spring 2019 - Project E1906. Refactor stage deadlines in Assignment.rb]]
*[[CSC/ECE 517 Spring 2019 - Project M1901 Implement missing WebAudio automation support]]
*[[CSC/ECE 517 Spring 2019 - Project E1917. Fix Code Climate issues in controllers with names beginning with P through Z]]
*[[CSC/ECE 517 Spring 2019 - Project E1921. Write tests for popup controller.rb]]
*[[CSC/ECE 517 Spring 2019 - M1902 Refactor bluetooth support for better maintainability]]
*[[CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb]]

CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb

2019-03-24T19:22:09Z

Jfwang2: /* Our work */

CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb

2019-03-24T19:21:28Z

Jfwang2:

CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb

2019-03-24T19:06:21Z

Jfwang2:

E1922 Write test for assessment360 controller.rb

2019-03-24T19:00:07Z

Jfwang2: moved E1922 Write test for assessment360 controller.rb to CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb: incorrect naming conventions

#REDIRECT [[CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb]]

CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb

2019-03-24T19:00:07Z

Jfwang2: moved E1922 Write test for assessment360 controller.rb to CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb: incorrect naming conventions

Will fill in later

CSC/ECE 517 Spring 2019 - E1922. Write tests for assessment360 controller.rb

2019-03-23T18:59:20Z

Jfwang2: Created page with "Will fill in later"

Will fill in later