Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps

2021-11-09T01:42:14Z

Cpsmith6: /* email */

== Description about project ==
This page is a description of Expertiza OSS project E2170 which aims to adequately test several files regarding the ResponseMap model. Here is a description of what response maps do:
*In Expertiza, response maps establish a relationship between a reviewer, a reviewee, and an object to be reviewed. The reviewer is an assignment_participant, the reviewee is an assignment_team, and the reviewed object is either an assignment or another response_map. Each (reviewer, reviewee) pair will have a separate response map. Every time a new review is performed (e.g, every round), a new Response object is created whose map_id is that response map.

The breakdown of the ResponseMap model can be found [https://expertiza.csc.ncsu.edu/index.php/Response_maps here]. There are several types of ResponseMaps that extend functionality of the original ResponseMap. None of which including the superclass are adequately tested. These files include:

* review_response_map.rb <--------- 92.5% coverage

* metareview_response_map.rb <------ 23.08% coverage

* teammate_review_response_map.rb <- no coverage

* response_map.rb <----------------- 74.47% coverage

This project aims to get all the response maps to at least a 90% level of coverage for every Response Map file by writing unit tests for each uncovered method listed in the next section.

== Team ==

* Connor Smith (cpsmith6)

* Abir Majumder (aamajumd)

* Quinn Dibble (qdibble)

* Alex Carruth (agcarrut)

== Test Files Involved ==
There are 4 test files involved in this project:
* review_response_map_spec.rb

* metareview_response_map_spec.rb

* teammate_review_response_map_spec.rb

* response_map_spec.rb
of these files, only review_response_map_spec.rb currently exists; the rest will be added.

== Methods Tested Per File ==

=== review_response_map_spec.rb ===
Currently this file is 92.5% covered and there are no plans to cover it further.

=== metareview_response_map_spec.rb ===
The functions for metareview_response_map.rb that will be tested are:
====get_all_versions====
This returns a sorted array of all the different versions of what is being reviewed in this response map. This means for a test, we will need to create a reviewer, a reviewee, several types of reviews of different versions to be sorted correctly.

[[File:E2170-get all versions.PNG]]

====contributor====
Returns the team associated with the ReviewResponseMap that is to be metareviewed. We will need to create a ReviewResponseMap that has a team associated with it. Then we must create MetareviewResponseMap that points to a created ReviewResponseMap via the reviewed_object_id attribute. We will test if it indeed returns the team associated with ReviewResponseMap.

[[File:E2170-contributor.PNG]]

====questionnaire====
Returns all questionnaires associated to the assignment of this MetareviewResponseMap that is of type 'MetareviewQuestionnaire'. We will need to create a valid MetareviewResponseMap including at least one MetareviewQuestionnaire that can be returned.

[[File:E2170-questionnaire.PNG]]

====get_title====
Returns string "Metareview". We will test if this string is the same as typed out.

[[File:E2170-get title.PNG]]

====exports====
This function takes 3 parameters: csv (the csv file that will contain the exported metareview information), parent_id (the assignment ID containing the requested metareviews), and _options. The function sends all the information about the metareviews to a csv file. We will test that the information is properly exported to the csv file. 
<pre>
def self.export(csv, parent_id, _options)
mappings = Assignment.find(parent_id).metareview_mappings
mappings = mappings.sort_by {|a| [a.review_mapping.reviewee.name, a.reviewee.name, a.reviewer.name] }
mappings.each do |map|
csv << [
map.review_mapping.reviewee.name,
map.reviewee.name,
map.reviewer.name
]
end
end
</pre>

====export_fields====
Takes a parameter called "_options" that returns the three field columns associated with metareviews to be exported for use by other controllers. We will test to see that these three columns are properly returned. 
<pre>
def self.export_fields(_options)
fields = ["contributor", "reviewed by", "metareviewed by"]
fields
end
</pre>

====import====
This function takes 3 parameters: row_hash (represents the hash of the metareview data we want to import), session, and id (representing the id of the assignment we want to import metareview data for). The function imports the data from the hash map, and if the information is input correctly, the data is extracted from the hash and creates a metareview for the requested assignment, otherwise it flashes an error saying the data was input incorrectly. We will test to make sure the imported data is properly converted into a metareview. 
[[File:E2170-import.jpg]]

====email====
This function takes 3 parameters: defn, _participant (the user who will be receiving the email), and assignment (the assignment associated with the metareview). The function sends an email to the participant when they have a new metareview to complete. We will test to make sure the email is sent to the correct participant. 
<pre>
def email(defn, _participant, assignment)
defn[:body][:type] = "Metareview"
reviewee_user = Participant.find(reviewee_id)
defn[:body][:obj_name] = assignment.name
defn[:body][:first_name] = User.find(reviewee_user.user_id).fullname
defn[:to] = User.find(reviewee_user.user_id).email
Mailer.sync_message(defn).deliver
end
</pre>

=== teammate_review_response_map_spec.rb ===
The functions for teammate_review_response_map.rb that will be tested are:
==== questionnaire ====
This function searches for a TeammateReviewQuestionnaire object and returns it.

[[File:E2170-teammate review response map-questionnaire.PNG]]

==== get_title ====
This function returns the string "Teammate Review".

[[File:E2170-teammate_review_response_map-get_title.png]]

==== teammate_response_report ====
This function returns the teammate response report given the reviewer ID.

[[File:E2170-teammate_review_response_map-teammate_response_report.PNG]]

==== email ====
This function sends a notification email to a student who has been reviewed by their teammate.

[[File:E2170-teammate_review_response_map-email.png]]

=== response_map_spec.rb ===
The functions for response_map.rb that will be tested are:
==== self.assessments_for(team) ====
Gets all submitted Review Responses or all regular Responses for a team, sorts the responses by version, and returns the latest Responses.

[[File:E2170-assessments_for.png]]

==== comparator ====
Compares two Responses version numbers and returns a -1,0, or 1 depending on which version number is greater. If there is no version number for the first response, -1 is returned, otherwise 1 is returned.

[[File:E2170-comparator.png]]

==== self.reviewer_assessments_for(team, reviewer) ====
Gets the Responses for a team reviewed by a specific reviewer and returns the latest response.

[[File:E2170-reviewer_assessments_for.png]]

==== metareviewed_by? ====
Returns whether the Response Map has been metareviewed

[[File:E2170-metareviewed_by.png]]

==== assign_metareviewer ====
This function is in charge of assigning a metareviewer to this review (i.e. a reviewer to review the review).

[[File:E2170-response_map-assign_metareviewer.png]]

==== find_team_member ====
This function returns the team that the reviewer is part of.

[[File:E2170-response_map-find_team_member.png]]

== Running Tests ==

<pre>
rspec ./spec/controllers/<test file name>
</pre>

CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps

2021-11-09T01:41:24Z

Cpsmith6: /* export_fields */

== Description about project ==
This page is a description of Expertiza OSS project E2170 which aims to adequately test several files regarding the ResponseMap model. Here is a description of what response maps do:
*In Expertiza, response maps establish a relationship between a reviewer, a reviewee, and an object to be reviewed. The reviewer is an assignment_participant, the reviewee is an assignment_team, and the reviewed object is either an assignment or another response_map. Each (reviewer, reviewee) pair will have a separate response map. Every time a new review is performed (e.g, every round), a new Response object is created whose map_id is that response map.

The breakdown of the ResponseMap model can be found [https://expertiza.csc.ncsu.edu/index.php/Response_maps here]. There are several types of ResponseMaps that extend functionality of the original ResponseMap. None of which including the superclass are adequately tested. These files include:

* review_response_map.rb <--------- 92.5% coverage

* metareview_response_map.rb <------ 23.08% coverage

* teammate_review_response_map.rb <- no coverage

* response_map.rb <----------------- 74.47% coverage

This project aims to get all the response maps to at least a 90% level of coverage for every Response Map file by writing unit tests for each uncovered method listed in the next section.

== Team ==

* Connor Smith (cpsmith6)

* Abir Majumder (aamajumd)

* Quinn Dibble (qdibble)

* Alex Carruth (agcarrut)

== Test Files Involved ==
There are 4 test files involved in this project:
* review_response_map_spec.rb

* metareview_response_map_spec.rb

* teammate_review_response_map_spec.rb

* response_map_spec.rb
of these files, only review_response_map_spec.rb currently exists; the rest will be added.

== Methods Tested Per File ==

=== review_response_map_spec.rb ===
Currently this file is 92.5% covered and there are no plans to cover it further.

=== metareview_response_map_spec.rb ===
The functions for metareview_response_map.rb that will be tested are:
====get_all_versions====
This returns a sorted array of all the different versions of what is being reviewed in this response map. This means for a test, we will need to create a reviewer, a reviewee, several types of reviews of different versions to be sorted correctly.

[[File:E2170-get all versions.PNG]]

====contributor====
Returns the team associated with the ReviewResponseMap that is to be metareviewed. We will need to create a ReviewResponseMap that has a team associated with it. Then we must create MetareviewResponseMap that points to a created ReviewResponseMap via the reviewed_object_id attribute. We will test if it indeed returns the team associated with ReviewResponseMap.

[[File:E2170-contributor.PNG]]

====questionnaire====
Returns all questionnaires associated to the assignment of this MetareviewResponseMap that is of type 'MetareviewQuestionnaire'. We will need to create a valid MetareviewResponseMap including at least one MetareviewQuestionnaire that can be returned.

[[File:E2170-questionnaire.PNG]]

====get_title====
Returns string "Metareview". We will test if this string is the same as typed out.

[[File:E2170-get title.PNG]]

====exports====
This function takes 3 parameters: csv (the csv file that will contain the exported metareview information), parent_id (the assignment ID containing the requested metareviews), and _options. The function sends all the information about the metareviews to a csv file. We will test that the information is properly exported to the csv file. 
<pre>
def self.export(csv, parent_id, _options)
mappings = Assignment.find(parent_id).metareview_mappings
mappings = mappings.sort_by {|a| [a.review_mapping.reviewee.name, a.reviewee.name, a.reviewer.name] }
mappings.each do |map|
csv << [
map.review_mapping.reviewee.name,
map.reviewee.name,
map.reviewer.name
]
end
end
</pre>

====export_fields====
Takes a parameter called "_options" that returns the three field columns associated with metareviews to be exported for use by other controllers. We will test to see that these three columns are properly returned. 
<pre>
def self.export_fields(_options)
fields = ["contributor", "reviewed by", "metareviewed by"]
fields
end
</pre>

====import====
This function takes 3 parameters: row_hash (represents the hash of the metareview data we want to import), session, and id (representing the id of the assignment we want to import metareview data for). The function imports the data from the hash map, and if the information is input correctly, the data is extracted from the hash and creates a metareview for the requested assignment, otherwise it flashes an error saying the data was input incorrectly. We will test to make sure the imported data is properly converted into a metareview. 
[[File:E2170-import.jpg]]

====email====
This function takes 3 parameters: defn, _participant (the user who will be receiving the email), and assignment (the assignment associated with the metareview). The function sends an email to the participant when they have a new metareview to complete. We will test to make sure the email is sent to the correct participant. 
[[File:E2170-email.jpg]]

=== teammate_review_response_map_spec.rb ===
The functions for teammate_review_response_map.rb that will be tested are:
==== questionnaire ====
This function searches for a TeammateReviewQuestionnaire object and returns it.

[[File:E2170-teammate review response map-questionnaire.PNG]]

==== get_title ====
This function returns the string "Teammate Review".

[[File:E2170-teammate_review_response_map-get_title.png]]

==== teammate_response_report ====
This function returns the teammate response report given the reviewer ID.

[[File:E2170-teammate_review_response_map-teammate_response_report.PNG]]

==== email ====
This function sends a notification email to a student who has been reviewed by their teammate.

[[File:E2170-teammate_review_response_map-email.png]]

=== response_map_spec.rb ===
The functions for response_map.rb that will be tested are:
==== self.assessments_for(team) ====
Gets all submitted Review Responses or all regular Responses for a team, sorts the responses by version, and returns the latest Responses.

[[File:E2170-assessments_for.png]]

==== comparator ====
Compares two Responses version numbers and returns a -1,0, or 1 depending on which version number is greater. If there is no version number for the first response, -1 is returned, otherwise 1 is returned.

[[File:E2170-comparator.png]]

==== self.reviewer_assessments_for(team, reviewer) ====
Gets the Responses for a team reviewed by a specific reviewer and returns the latest response.

[[File:E2170-reviewer_assessments_for.png]]

==== metareviewed_by? ====
Returns whether the Response Map has been metareviewed

[[File:E2170-metareviewed_by.png]]

==== assign_metareviewer ====
This function is in charge of assigning a metareviewer to this review (i.e. a reviewer to review the review).

[[File:E2170-response_map-assign_metareviewer.png]]

==== find_team_member ====
This function returns the team that the reviewer is part of.

[[File:E2170-response_map-find_team_member.png]]

== Running Tests ==

<pre>
rspec ./spec/controllers/<test file name>
</pre>

CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps

2021-11-09T01:41:04Z

Cpsmith6: /* exports */

== Description about project ==
This page is a description of Expertiza OSS project E2170 which aims to adequately test several files regarding the ResponseMap model. Here is a description of what response maps do:
*In Expertiza, response maps establish a relationship between a reviewer, a reviewee, and an object to be reviewed. The reviewer is an assignment_participant, the reviewee is an assignment_team, and the reviewed object is either an assignment or another response_map. Each (reviewer, reviewee) pair will have a separate response map. Every time a new review is performed (e.g, every round), a new Response object is created whose map_id is that response map.

The breakdown of the ResponseMap model can be found [https://expertiza.csc.ncsu.edu/index.php/Response_maps here]. There are several types of ResponseMaps that extend functionality of the original ResponseMap. None of which including the superclass are adequately tested. These files include:

* review_response_map.rb <--------- 92.5% coverage

* metareview_response_map.rb <------ 23.08% coverage

* teammate_review_response_map.rb <- no coverage

* response_map.rb <----------------- 74.47% coverage

This project aims to get all the response maps to at least a 90% level of coverage for every Response Map file by writing unit tests for each uncovered method listed in the next section.

== Team ==

* Connor Smith (cpsmith6)

* Abir Majumder (aamajumd)

* Quinn Dibble (qdibble)

* Alex Carruth (agcarrut)

== Test Files Involved ==
There are 4 test files involved in this project:
* review_response_map_spec.rb

* metareview_response_map_spec.rb

* teammate_review_response_map_spec.rb

* response_map_spec.rb
of these files, only review_response_map_spec.rb currently exists; the rest will be added.

== Methods Tested Per File ==

=== review_response_map_spec.rb ===
Currently this file is 92.5% covered and there are no plans to cover it further.

=== metareview_response_map_spec.rb ===
The functions for metareview_response_map.rb that will be tested are:
====get_all_versions====
This returns a sorted array of all the different versions of what is being reviewed in this response map. This means for a test, we will need to create a reviewer, a reviewee, several types of reviews of different versions to be sorted correctly.

[[File:E2170-get all versions.PNG]]

====contributor====
Returns the team associated with the ReviewResponseMap that is to be metareviewed. We will need to create a ReviewResponseMap that has a team associated with it. Then we must create MetareviewResponseMap that points to a created ReviewResponseMap via the reviewed_object_id attribute. We will test if it indeed returns the team associated with ReviewResponseMap.

[[File:E2170-contributor.PNG]]

====questionnaire====
Returns all questionnaires associated to the assignment of this MetareviewResponseMap that is of type 'MetareviewQuestionnaire'. We will need to create a valid MetareviewResponseMap including at least one MetareviewQuestionnaire that can be returned.

[[File:E2170-questionnaire.PNG]]

====get_title====
Returns string "Metareview". We will test if this string is the same as typed out.

[[File:E2170-get title.PNG]]

====exports====
This function takes 3 parameters: csv (the csv file that will contain the exported metareview information), parent_id (the assignment ID containing the requested metareviews), and _options. The function sends all the information about the metareviews to a csv file. We will test that the information is properly exported to the csv file. 
<pre>
def self.export(csv, parent_id, _options)
mappings = Assignment.find(parent_id).metareview_mappings
mappings = mappings.sort_by {|a| [a.review_mapping.reviewee.name, a.reviewee.name, a.reviewer.name] }
mappings.each do |map|
csv << [
map.review_mapping.reviewee.name,
map.reviewee.name,
map.reviewer.name
]
end
end
</pre>

====export_fields====
Takes a parameter called "_options" that returns the three field columns associated with metareviews to be exported for use by other controllers. We will test to see that these three columns are properly returned. 
[[File:E2170-export_fields.jpg]]

====import====
This function takes 3 parameters: row_hash (represents the hash of the metareview data we want to import), session, and id (representing the id of the assignment we want to import metareview data for). The function imports the data from the hash map, and if the information is input correctly, the data is extracted from the hash and creates a metareview for the requested assignment, otherwise it flashes an error saying the data was input incorrectly. We will test to make sure the imported data is properly converted into a metareview. 
[[File:E2170-import.jpg]]

====email====
This function takes 3 parameters: defn, _participant (the user who will be receiving the email), and assignment (the assignment associated with the metareview). The function sends an email to the participant when they have a new metareview to complete. We will test to make sure the email is sent to the correct participant. 
[[File:E2170-email.jpg]]

=== teammate_review_response_map_spec.rb ===
The functions for teammate_review_response_map.rb that will be tested are:
==== questionnaire ====
This function searches for a TeammateReviewQuestionnaire object and returns it.

[[File:E2170-teammate review response map-questionnaire.PNG]]

==== get_title ====
This function returns the string "Teammate Review".

[[File:E2170-teammate_review_response_map-get_title.png]]

==== teammate_response_report ====
This function returns the teammate response report given the reviewer ID.

[[File:E2170-teammate_review_response_map-teammate_response_report.PNG]]

==== email ====
This function sends a notification email to a student who has been reviewed by their teammate.

[[File:E2170-teammate_review_response_map-email.png]]

=== response_map_spec.rb ===
The functions for response_map.rb that will be tested are:
==== self.assessments_for(team) ====
Gets all submitted Review Responses or all regular Responses for a team, sorts the responses by version, and returns the latest Responses.

[[File:E2170-assessments_for.png]]

==== comparator ====
Compares two Responses version numbers and returns a -1,0, or 1 depending on which version number is greater. If there is no version number for the first response, -1 is returned, otherwise 1 is returned.

[[File:E2170-comparator.png]]

==== self.reviewer_assessments_for(team, reviewer) ====
Gets the Responses for a team reviewed by a specific reviewer and returns the latest response.

[[File:E2170-reviewer_assessments_for.png]]

==== metareviewed_by? ====
Returns whether the Response Map has been metareviewed

[[File:E2170-metareviewed_by.png]]

==== assign_metareviewer ====
This function is in charge of assigning a metareviewer to this review (i.e. a reviewer to review the review).

[[File:E2170-response_map-assign_metareviewer.png]]

==== find_team_member ====
This function returns the team that the reviewer is part of.

[[File:E2170-response_map-find_team_member.png]]

== Running Tests ==

<pre>
rspec ./spec/controllers/<test file name>
</pre>

CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps

2021-11-08T20:07:05Z

Cpsmith6: /* exports */

CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps

2021-11-08T20:06:31Z

Cpsmith6: /* metareview_response_map_spec.rb */

File:E2170-import.jpg

2021-11-08T20:01:17Z

Cpsmith6: import function flowchart for metareview_response_map.rb

import function flowchart for metareview_response_map.rb

File:E2170-export fields.jpg

2021-11-08T20:00:45Z

Cpsmith6: export_fields function for metareview_response_map.rb

export_fields function for metareview_response_map.rb

File:E2170-export.jpg

2021-11-08T20:00:13Z

Cpsmith6: export function for metareview_response_map.rb

export function for metareview_response_map.rb

File:E2170-email.jpg

2021-11-08T19:59:36Z

Cpsmith6: email function in metareview_response_map

email function in metareview_response_map

CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps

2021-11-08T19:46:15Z

Cpsmith6: /* email */

CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps

2021-11-08T19:24:57Z

Cpsmith6: /* export_fields */

CSC/ECE 517 Fall 2021 - E2170. Testing - Response Maps

2021-11-08T19:23:31Z

Cpsmith6: /* metareview_response_map_spec.rb */

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-21T03:27:03Z

Cpsmith6: /* Results */

== About Expertiza==

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework that supports submission across different document types, including theURLs and wiki pages. It allows the instructor 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 in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions.

== Description about project ==
This page is a description of Expertiza OSS project E2126 which refactoring the account_request_controller.rb file. This file allows Super Administrators to manage the approval process for new users. Our job was to refactor some of the longer methods in this file, make error messages more intuitive, and add a security captcha to the approval/rejection process.

=== Team ===

Connor Smith (cpsmith6)

Abir Majumder (aamajumd)

Joshua Myers (jamyers3)

=== Files Involved ===

account_request_controller.rb

=== Running Tests ===

<pre>
rspec ./spec/controllers/account_request_controller.rb
</pre>

== Relevant Methods ==

* action_allowed?
* create_approved_user
* create_requested_user_record

=== action_allowed? ===

This method validates if the user is allowed to be redirected to the appropriate page. The task for this project is to add a captcha system before the user requests new. This happens when the user hits the "Request account" button on the login page. This project's repo already has the "recaptcha" gem installed. Future developers need to keep in mind that functionality of the captcha depends on the developer updating the site key and secret key of the Google ReCaptcha API. Installation of the gem and getting the key instructions can be found [https://github.com/ambethia/recaptcha here].

There was one change to the frontend to display the captcha at _login.html.erb.

'''Front end change /app/views/_login.html.erb'''
<pre>
...
...
<% end %>

<%= link_to "Request account",{:controller => 'account_request',:role => "Instructor", :action => 'new'}, :class => 'btn btn-danger', :style => 'color:white;width:100%;margin-left:auto;margin-right:auto;' %>
<div>
<%= recaptcha_tags %> <<--=-----displays recaptcha widget
</div>

 
</div>

<% end %>
</pre>

'''action_allowed? changes'''
<pre>
def captcha_test
valid = true
@something
if verify_recaptcha(model: @something) == true
valid = true
end
return valid
end

def action_allowed?
case params[:action]
when 'list_pending_requested'
current_user_has_admin_privileges?
when 'new'
captcha_test
when 'create_requested_user_record'
true
when 'keys'
current_user_has_student_privileges?
else
current_user_has_ta_privileges?
end
end
</pre>

=== create_approved_user ===

This method allows a Super Admin to approve or reject new users, and gives them an error message if the incorrect steps are taken during that process

==== Original Method ====
<pre>
def create_approved_user
if params[:selection] == nil
flash[:error] = "Please Approve or Reject before submitting"
redirect_to action: 'list_pending_requested'
return
end
is_approved = (params[:commit] == "Accept"? "Approved" : "Rejected")
users = params[:selection]
users.each do |user|
requested_user = AccountRequest.find_by(id: user.first)
requested_user.status = is_approved
if requested_user.status.nil?
flash[:error] = "Please Approve or Reject before submitting"
elsif requested_user.update_attributes(params[:user])
flash[:success] = "The user \"#{requested_user.name}\" has been successfully updated."
end
if requested_user.status == "Approved"
new_user = User.new
new_user.name = requested_user.name
new_user.role_id = requested_user.role_id
new_user.institution_id = requested_user.institution_id
new_user.fullname = requested_user.fullname
new_user.email = requested_user.email
new_user.parent_id = session[:user].id
new_user.timezonepref = User.find_by(id: new_user.parent_id).timezonepref
if new_user.save
password = new_user.reset_password
# Mail is sent to the user with a new password
prepared_mail = MailerHelper.send_mail_to_user(new_user, "Your Expertiza account and password have been created.", "user_welcome", password)
prepared_mail.deliver_now
flash[:success] = "A new password has been sent to new user's e-mail address."
undo_link("The user \"#{requested_user.name}\" has been successfully created. ")
else
foreign
end
elsif requested_user.status == "Rejected"
# If the user request has been rejected, a flash message is shown and redirected to review page
if requested_user.update_columns(status: is_approved)
flash[:success] = "The user \"#{requested_user.name}\" has been Rejected."
# redirect_to action: 'list_pending_requested'
# return
else
flash[:error] = "Error processing request."
end
end
end
redirect_to action: 'list_pending_requested'
end
</pre>

==== Refactored Method ====

This method was refactored so the creation of the new user is handled in a separate method called '''"user_new"'''

<pre>
def create_approved_user
if params[:selection] == nil
flash[:error] = "Please Approve or Reject before submitting"
redirect_to action: 'list_pending_requested'
return
end
is_approved = (params[:commit] == "Accept"? "Approved" : "Rejected")
users = params[:selection]
users.each do |user|
requested_user = AccountRequest.find_by(id: user.first)
requested_user.status = is_approved
puts "Here"
if requested_user.status.nil?
flash[:error] = "Please Approve or Reject before submitting"
elsif requested_user.update_attributes(params[:user])
flash[:success] = "The user \"#{requested_user.name}\" has been successfully updated."
end
if requested_user.status == "Approved"
user_new(requested_user)
elsif requested_user.status == "Rejected"
# If the user request has been rejected, a flash message is shown and redirected to review page
if requested_user.update_columns(status: is_approved)
flash[:success] = "The user \"#{requested_user.name}\" has been Rejected."
# redirect_to action: 'list_pending_requested'
# return
else
flash[:error] = "Error processing request."
end
end
end
redirect_to action: 'list_pending_requested'
end

def user_new(requested_user)
puts requested_user.inspect
new_user = User.new
new_user.name = requested_user.name
new_user.role_id = requested_user.role_id
new_user.institution_id = requested_user.institution_id
new_user.fullname = requested_user.fullname
new_user.email = requested_user.email
new_user.parent_id = session[:user].id
new_user.timezonepref = User.find_by(id: new_user.parent_id).timezonepref
if new_user.save
password = new_user.reset_password
# Mail is sent to the user with a new password
prepared_mail = MailerHelper.send_mail_to_user(new_user, "Your Expertiza account and password have been created.", "user_welcome", password)
prepared_mail.deliver_now
flash[:success] = "A new password has been sent to new user's e-mail address."
undo_link("The user \"#{requested_user.name}\" has been successfully created. ")
else
foreign
end
end
</pre>

=== create_requested_user_record ===

create_requested_user creates a new account request for a user (if they are not a duplicate user) so that it may be approved by a higher level user.

==== Original Method ====

<pre>
def create_requested_user_record

requested_user = AccountRequest.new(requested_user_params)
#An object is created with respect to AccountRequest model inorder to populate the users information when account is requested

if params[:user][:institution_id].empty?
institution = Institution.find_or_create_by(name: params[:institution][:name])
requested_user.institution_id = institution.id
end
#If user enters others and adds a new institution, an institution id will be created with respect to the institution model.
#This institution_attribute will be added to the AccountRequest model under institution_id attribute!

#
requested_user.status = 'Under Review'
#The status is by default 'Under Review' until the super admin approves or rejects

user_existed = User.find_by(name: requested_user.name) or User.find_by(name: requested_user.email)
# default to instructor role
if requested_user.role_id == nil
requested_user.role_id = Role.where(:name => "Instructor")[0].id
end
requested_user_saved = requested_user.save
#Stores a boolean value with respect to whether the user data is saved or not

if !user_existed and requested_user_saved
super_users = User.joins(:role).where('roles.name = ?', 'Super-Administrator')
super_users.each do |super_user|
prepared_mail = MailerHelper.send_mail_to_all_super_users(super_user, requested_user, 'New account Request')
prepared_mail.deliver
end
#Notifying an email to the administrator regarding the new user request!
ExpertizaLogger.info LoggerMessage.new(controller_name, requested_user.name, 'The account you are requesting has been created successfully.', request)
flash[:success] = "User signup for \"#{requested_user.name}\" has been successfully requested."
redirect_to '/instructions/home'
#Print out the acknowledgement message to the user and redirect to /instructors/home page when successful

return
elsif user_existed
flash[:error] = "The account you are requesting has already existed in Expertiza."
#If the user account already exists, log error to the user
else
flash[:error] = requested_user.errors.full_messages.to_sentence
#If saving in the AccountRequests model has failed
end
ExpertizaLogger.error LoggerMessage.new(controller_name, requested_user.name, flash[:error], request)
redirect_to controller: 'account_request', action: 'new', role: 'Student'
#if the first if clause fails, redirect back to the account requests page!
end
</pre>

==== Refactored Method ====

The new create_requested_user_record now only handles the different cases that can happen when a user requests an account (New user and request goes through, duplicate user and request doesn't go through, or some other error in the saving process. The new method save_requested_user creates the request object, validates it has all needed fields and tries to save it to the database. The new method notify_supers_new_request sends an email to the Super-Administrators that new user account request has been successfully created. Some variable names and error messages have been reworded to improve readability as well.

<pre>
def create_requested_user_record
requested_user = AccountRequest.new(requested_user_params)
#An object is created with respect to AccountRequest model inorder to populate the users information when account is requested
user_exists = User.find_by(name: requested_user.name) or User.find_by(name: requested_user.email)
requested_user_saved = save_requested_user(requested_user, params)
#Stores a boolean value with respect to whether the user data is saved or not
if !user_exists and requested_user_saved
notify_supers_new_request(requested_user)
redirect_to '/instructions/home'
return
elsif user_exists
flash[:error] = "The account you are requesting already exists in Expertiza."
#If the user account already exists, log error to the user
else
flash[:error] = requested_user.errors.full_messages.to_sentence
#If saving in the AccountRequests model has failed
end
ExpertizaLogger.error LoggerMessage.new(controller_name, requested_user.name, flash[:error], request)
redirect_to controller: 'account_request', action: 'new', role: 'Student'
#if the first if clause fails, redirect back to the account requests page!
end

def save_requested_user(requested_user, params)
if params[:user][:institution_id].empty?
institution = Institution.find_or_create_by(name: params[:institution][:name])
requested_user.institution_id = institution.id
end
#If user enters others and adds a new institution, an institution id will be created with respect to the institution model.
#This institution_attribute will be added to the AccountRequest model under institution_id attribute!
requested_user.status = 'Under Review'
#The status is by default 'Under Review' until the super admin approves or rejects
# default to instructor role
if requested_user.role_id == nil
requested_user.role_id = Role.where(:name => "Instructor")[0].id
end
return requested_user.save
end

def notify_supers_new_request(requested_user)
super_users = User.joins(:role).where('roles.name = ?', 'Super-Administrator')
super_users.each do |super_user|
prepared_mail = MailerHelper.send_mail_to_all_super_users(super_user, requested_user, 'New account Request')
prepared_mail.deliver
end
#Notifying an email to the administrator regarding the new user request!
ExpertizaLogger.info LoggerMessage.new(controller_name, requested_user.name, 'The account you are requesting has been created successfully.', request)
flash[:success] = "User signup for \"#{requested_user.name}\" has been successfully requested."
#Print out the acknowledgement message to the user and redirect to /instructors/home page when successful
end
</pre>

== Results ==

12 out of 12 tests in the account_request_controller_spec.rb test file.

Here is a image of our tests passing: 
[[File:Passing Test.jpg]]

=== Relevant Links ===

Main Expertiza Repository can be found [https://github.com/expertiza/expertiza here].

Our forked Repository can be found [https://github.com/majuabir/expertiza/tree/beta here].

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:29:21Z

Cpsmith6: /* Results */

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:29:00Z

Cpsmith6: /* Results */

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:28:30Z

Cpsmith6:

File:Passing Test.jpg

2021-10-19T23:27:42Z

Cpsmith6: Passing tests for account_request_controller

Passing tests for account_request_controller

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:26:40Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:19:22Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:18:20Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:15:27Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:13:33Z

Cpsmith6: /* Refactored Method */

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:12:55Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:11:05Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:08:59Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T23:05:59Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T22:59:43Z

Cpsmith6:

CSC/ECE 517 Fall 2021 - E2126. Refactor account request controller.rb

2021-10-19T22:54:13Z

Cpsmith6: Created page with "* CSC/ECE 517 Fall 2021 - E2126. Refactor account_request_controller.rb"

* [[CSC/ECE 517 Fall 2021 - E2126. Refactor account_request_controller.rb]]

CSC/ECE 517 Fall 2021

2021-10-19T22:53:48Z

Cpsmith6:

== OSS Projects ==
* [[CSC/ECE 517 Fall 2021 - {$num}. {$desc.title}]]
* [[CSC/ECE 517 Fall 2021 - E2128. Refactor student_quizzes_controller.rb & late_policies_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2132. Add tests cases for review mapping helper.rb]]
* [[CSC/ECE 517 Fall 2021 - E2134. Write unit tests for admin_controller.rb and institution_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2138. Auto-generate submission directory names based on assignment]]
* [[CSC/ECE 517 Fall 2021 - E2142. Improve e-mail notifications]]
* [[CSC/ECE 517 Fall 2021 - E2133. Write tests for popup_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2120. Refactor reputation_web_service_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2139. Remove multiple topics at a time]]
* [[CSC/ECE 517 Fall 2021 - E2131. Improve assessment360_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2121. Refactor suggestion_controller.rb]]
* [[CSC/ECE 517 Fall 2021 - E2126. Refactor account_request_controller.rb]]