Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-05-01T20:49:09Z

Sdamulu: /* Future Scope */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==UML Diagrams==

==='''Reviewers use case'''===

:: [[File:Reviewer_usecase.png|300px]] 

==='''Author's use case'''===

:: [[File:Author_usecase.png|300px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
email_author_reviewers(subject, body, email) will be added which can be used in both the workflows to send an Email.
 
From the Reviewer's perspective, the following files will be updated and a new view will be created.

1. '''app/views/response/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/response_controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/response/author.html.erb :''' This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. '''app/views/student_task/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/student_task controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/student_task/email_reviewers.html.erb :''' This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Assignment_page.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Implememtation==

The following are the screenshots of the changes that we made in the codebase.

===Send Email Method in MailerHelper===
We created a new method called send_mail_to_author_reviewers(subject, body, email), which accepts 3 parameters; subject, body and email. We used the same method for both sending emails to authors and reviewers.

[[File:Email_method.png|800px]] 

===Email from Reviewer to Author===
====View====
To create the author view, we created a new view called author.html.erb and created a form in that file, which asks the user to enter the subject and body.
[[File:Author_view.png|800px]] 

====Controller====
We created a method called send_email in the response_controller which handles the functionality for sending an email. The method also contains validations that throw an error if the user is trying to submit the form without filling out the subject or body. If there are no validation errors, we pass the subject, body, and email from the view to the controller and send them to a method called send_mail_to_author_reviewers which is a part of MailerHelper. This method is responsible for sending emails to the author.

[[File:Send_email_author.png|1000px]] 

===Email from Author to Reviewers===
====View====
To create the reviewer view, we created a new view called email_reviewers.html.erb where we created a form that asks the user to enter the subject and body of the email.
[[File:Author_view.png|800px]] 

====Controller====
To send an email to all the reviewers, we created a method called send_email in the student_task_controller. The method also contains validations that throw an error if the user is trying to submit the form without filling out the subject or body. If there are no validation errors, we go ahead and pass the parameters; subject, body, and reviewer.email to the send_mail_to_author_reviewers method from MailerHelper.

[[File:Send_email_reviewer.png|1000px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the response_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Future Scope==

1. Currently, only a subject and a text message are provided to send an Email, in future the above functionality can be extended to include attachments in the Email. For example, Reviewer can send an image/screenshot for a failure they have come across to the Author.

2. New functionality to send messages within expertiza

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-05-01T20:46:40Z

Sdamulu:

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==UML Diagrams==

==='''Reviewers use case'''===

:: [[File:Reviewer_usecase.png|300px]] 

==='''Author's use case'''===

:: [[File:Author_usecase.png|300px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
email_author_reviewers(subject, body, email) will be added which can be used in both the workflows to send an Email.
 
From the Reviewer's perspective, the following files will be updated and a new view will be created.

1. '''app/views/response/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/response_controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/response/author.html.erb :''' This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. '''app/views/student_task/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/student_task controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/student_task/email_reviewers.html.erb :''' This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Assignment_page.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Implememtation==

The following are the screenshots of the changes that we made in the codebase.

===Send Email Method in MailerHelper===
We created a new method called send_mail_to_author_reviewers(subject, body, email), which accepts 3 parameters; subject, body and email. We used the same method for both sending emails to authors and reviewers.

[[File:Email_method.png|800px]] 

===Email from Reviewer to Author===
====View====
To create the author view, we created a new view called author.html.erb and created a form in that file, which asks the user to enter the subject and body.
[[File:Author_view.png|800px]] 

====Controller====
We created a method called send_email in the response_controller which handles the functionality for sending an email. The method also contains validations that throw an error if the user is trying to submit the form without filling out the subject or body. If there are no validation errors, we pass the subject, body, and email from the view to the controller and send them to a method called send_mail_to_author_reviewers which is a part of MailerHelper. This method is responsible for sending emails to the author.

[[File:Send_email_author.png|1000px]] 

===Email from Author to Reviewers===
====View====
To create the reviewer view, we created a new view called email_reviewers.html.erb where we created a form that asks the user to enter the subject and body of the email.
[[File:Author_view.png|800px]] 

====Controller====
To send an email to all the reviewers, we created a method called send_email in the student_task_controller. The method also contains validations that throw an error if the user is trying to submit the form without filling out the subject or body. If there are no validation errors, we go ahead and pass the parameters; subject, body, and reviewer.email to the send_mail_to_author_reviewers method from MailerHelper.

[[File:Send_email_reviewer.png|1000px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the response_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Future Scope==

Currently, only a subject and a text message are provided to send an Email, in future the above functionality can be extended to include attachments in the Email. For example, Reviewer can send an image/screenshot for a failure they have come across to the Author.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-05-01T20:39:47Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==UML Diagrams==

==='''Reviewers use case'''===

:: [[File:Reviewer_usecase.png|300px]] 

==='''Author's use case'''===

:: [[File:Author_usecase.png|300px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
email_author_reviewers(subject, body, email) will be added which can be used in both the workflows to send an Email.
 
From the Reviewer's perspective, the following files will be updated and a new view will be created.

1. '''app/views/response/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/response_controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/response/author.html.erb :''' This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. '''app/views/student_task/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/student_task controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/student_task/email_reviewers.html.erb :''' This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Assignment_page.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Implememtation==

The following are the screenshots of the changes that we made in the codebase.

===Send Email Method in MailerHelper===
We created a new method called send_mail_to_author_reviewers(subject, body, email), which accepts 3 parameters; subject, body and email. We used the same method for both sending emails to authors and reviewers.

[[File:Email_method.png|800px]] 

===Email from Reviewer to Author===
====View====
To create the author view, we created a new view called author.html.erb and created a form in that file, which asks the user to enter the subject and body.
[[File:Author_view.png|800px]] 

====Controller====
We created a method called send_email in the response_controller which handles the functionality for sending an email. The method also contains validations that throw an error if the user is trying to submit the form without filling out the subject or body. If there are no validation errors, we pass the subject, body, and email from the view to the controller and send them to a method called send_mail_to_author_reviewers which is a part of MailerHelper. This method is responsible for sending emails to the author.

[[File:Send_email_author.png|1000px]] 

===Email from Author to Reviewers===
====View====
To create the reviewer view, we created a new view called email_reviewers.html.erb where we created a form that asks the user to enter the subject and body of the email.
[[File:Author_view.png|800px]] 

====Controller====
To send an email to all the reviewers, we created a method called send_email in the student_task_controller. The method also contains validations that throw an error if the user is trying to submit the form without filling out the subject or body. If there are no validation errors, we go ahead and pass the parameters; subject, body, and reviewer.email to the send_mail_to_author_reviewers method from MailerHelper.

[[File:Send_email_reviewer.png|1000px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the response_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-05-01T18:21:26Z

Sdamulu: /* Design Pattern */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==UML Diagrams==

==='''Reviewers use case'''===

:: [[File:Reviewer_usecase.png|300px]] 

==='''Author's use case'''===

:: [[File:Author_usecase.png|300px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'''def send_mail_to_user(user, subject, partial_name, password)''' can be used to send the email to an another from reviewer and
'''def send_mail_to_assigned_reviewers''' can be used to send emails to all reviewers from an author.
 
From the Reviewer's perspective, the following files will be updated and a new partial will be created to render the new view.

1. '''app/views/response/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/response_controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/response/email_author.html.erb :''' This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. '''app/views/student_task/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/student_task controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/student_task/email_reviewers.html.erb :''' This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Assignment_page.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the response_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T21:48:52Z

Sdamulu: /* Proposed Changes */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==UML Diagrams==

==='''Reviewers use case'''===

:: [[File:Reviewer_usecase.png|300px]] 

==='''Author's use case'''===

:: [[File:Author_usecase.png|300px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'''def send_mail_to_user(user, subject, partial_name, password)''' can be used to send the email to an another from reviewer and
'''def send_mail_to_assigned_reviewers''' can be used to send emails to all reviewers from an author.
 
From the Reviewer's perspective, the following files will be updated and a new partial will be created to render the new view.

1. '''app/views/response/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/response_controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/response/email_author.html.erb :''' This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. '''app/views/student_task/view.html.erb :''' link to the new view will be added to this file. 
2. '''app/controllers/student_task controller.rb :''' implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. '''app/views/student_task/email_reviewers.html.erb :''' This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the response_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T21:10:32Z

Sdamulu: /* RSPEC Testing */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send emails to all reviewers from an author.
 
From the Reviewer's perspective, the following files will be updated and a new partial will be created to render the new view.

1. app/views/response/view.html.erb : link to the new view will be added to this file. 
2. app/controllers/response_controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/response/email_author.html.erb : This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added to this file. 
2. app/controllers/student_task controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_task/email_reviewers.html.erb : This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the response_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T21:10:14Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send emails to all reviewers from an author.
 
From the Reviewer's perspective, the following files will be updated and a new partial will be created to render the new view.

1. app/views/response/view.html.erb : link to the new view will be added to this file. 
2. app/controllers/response_controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/response/email_author.html.erb : This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added to this file. 
2. app/controllers/student_task controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_task/email_reviewers.html.erb : This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the student_review_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T21:09:54Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send emails to all reviewers from an author.
 
From the Reviewer's perspective, the following files will be updated and a new partial will be created to render the new view.

1. app/views/response/view.html.erb : link to the new view will be added to this file. 
2. app/controllers/response_controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/response/email_author.html.erb : This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added to this file. 
2. app/controllers/student_task controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_reviewers.html.erb : This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the student_review_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T21:09:18Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send emails to all reviewers from an author.
 
From the Reviewer's perspective, the following files will be updated and a new partial will be created to render the new view.

1. app/views/response/view.html.erb : link to the new view will be added to this file. 
2. app/controllers/response_controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/response/email_author.html.erb ( new partial) : This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added to this file. 
2. app/controllers/student_task controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_reviwers.html.erb ( new partial): This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the student_review_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T21:05:21Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send emails to all reviewers from an author.
 
From the Reviewer's perspective, the following files will be updated and a new partial will be created to render the new view.

1. app/views/student_review/list.html.erb : link to the new view will be added to this file. 
2. app/controllers/student_review_controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_author.html.erb ( new partial) : This is the new UI page. A mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added to this file. 
2. app/controllers/student_task controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_reviwers.html.erb ( new partial): This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_SS.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the student_review_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T21:02:11Z

Sdamulu: /* RSPEC Testing */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send emails to all reviewers from an author.
 
From the Reviewer's perspective, the following files will be updated and a new partial will be created to render the new view.

1. app/views/student_review/list.html.erb : link to the new view will be added to this file. 
2. app/controllers/student_review_controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_author.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 
 

From Author's perspective, the following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added to this file. 
2. app/controllers/student_task controller.rb : implementation of the action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_reviwers.html.erb ( new partial): This is the new UI page. A mockup for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Author_Screenshot.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the student_review_controller.rb and student_task controller.rb.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T20:52:21Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send email to all reviewers from an author.
 
From Reviewer perspective, following files will be updated and a new partial will be created to render the new view.

1. app/views/student_review/list.html.erb : link to the new view will be added in this file. 
2. app/controllers/student_review_controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_author.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 
 

From Author perspective, following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added in this file. 
2. app/controllers/student_task controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_reviwers.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T20:51:56Z

Sdamulu: /* Proposed Changes */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send email to all reviewers from an author.

From Reviewer perspective, following files will be updated and a new partial will be created to render the new view.

1. app/views/student_review/list.html.erb : link to the new view will be added in this file. 
2. app/controllers/student_review_controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_author.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 
 

From Author perspective, following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added in this file. 
2. app/controllers/student_task controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_reviwers.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T20:51:22Z

Sdamulu: /* Proposed Changes */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send email to all reviewers from an author.

From Reviewer perspective, following files will be updated and a new partial will be created to render the new view.

1. app/views/student_review/list.html.erb : link to the new view will be added in this file. 
2. app/controllers/student_review_controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_author.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 
 

From Author perspective, following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added in this file. 
2. app/controllers/student_task controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_reviwers.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T20:51:00Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send email to all reviewers from an author.

From Reviewer perspective, following files will be updated and a new partial will be created to render the new view.

1. app/views/student_review/list.html.erb : link to the new view will be added in this file. 
2. app/controllers/student_review_controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_author.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 

From Author perspective, following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added in this file. 
2. app/controllers/student_task controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here. 
3. app/views/student_review/email_reviwers.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section. 

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T20:48:33Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which makes use of ActionMailer and contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send email to all reviewers from an author.

From Reviewer perspective, following files will be updated and a new partial will be created to render the new view.

1. app/views/student_review/list.html.erb : link to the new view will be added in this file.
2. app/controllers/student_review_controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here.
3. app/views/student_review/email_author.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section.

From Author perspective, following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added in this file.
2. app/controllers/student_task controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here.
3. app/views/student_review/email_reviwers.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section.

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T20:47:09Z

Sdamulu: /* Code Implementation */

==Introduction==

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Flowchart==

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|1000px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|1000px]] 

==Proposed Changes==
===Code Implementation===

Expertiza code base already contains a module 'MailerHelper' which contains methods to send emails to different users.
'def send_mail_to_user(user, subject, partial_name, password)' can be used to send the email to an another from reviewer and
'def send_mail_to_assigned_reviewers' can be used to send email to all reviewers from an author.

From Reviewer perspective, following files will be updated and a new partial will be created to render the new view.

1. app/views/student_review/list.html.erb : link to the new view will be added in this file.
2. app/controllers/student_review_controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here.
3. app/views/student_review/email_author.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section.

From Author perspective, following files will be updated and a new partial will be created to render the new view.

1. App/views/student_task/list.html.erb : link to the new view will be added in this file.
2. app/controllers/student_task controller.rb : implementation of action method for the send button will be added here. Methods from MailerHelper will be used here.
3. app/views/student_review/email_reviwers.html.erb ( new partial) : This is the new UI page. Mock up for the view is presented in the UI section.

===UI===
As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|800px]] 

[[File:Msg-to-A.png|800px]] 

==Testing==

===RSPEC Testing===

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

We are planning to cover the following test cases:

1. Author View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to reviewers",
the author must be redirected to email_reviewers_view.
2. Check if the recipients of the email are indeed the reviewers of the authors' work.

2. Reviewer View:

1. Upon Clicking on the link which is placed on the right corner of the page called "send email to author",
the reviewer must be redirected to email_authors_view.
2. Check if the recipients of the email are indeed the authors of the reviewed work.

We will also be checking the below two edge cases:

1. Author View:
1. Once the email is sent, the author should be redirected to the assignment page with the corresponding success
or failure message
2. Reviewer View:
2. Once the email is sent, the author should be redirected to the "others work" page with the corresponding success
or failure message

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==Team Members==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek Arvindkumar Upadhyay (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-11T20:18:49Z

Sdamulu:

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:46:46Z

Sdamulu: /* Flowchart */

==Introduction==

===Expertiza Background ===
Expertiza is a web application where students can submit and peer-review learning objects (articles, codes, websites, etc). Instructors add and grade the assignments submitted by students to Expertiza. Students can be assigned in teams based on their selection of the topics. It has functionalities such as peer reviews in which students can provide feedback on other's work which helps peer in better developing the project. It is supported by the National Science Foundation.

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Proposed Changes==

As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|800px]] 

[[File:Message-to-R.png|800px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|800px]] 

[[File:Msg-to-A.png|800px]] 

===Flowchart===

'''Author's View''' : The flow for authors to email reviewers regarding the work they have been reviewed for:

[[File:Author's view flowchart.jpg|800px]] 

'''Reviewer's View''' : The flow for reviewers to email authors whose work they have reviewed:

[[File:Reviewers_View_Flowchart.jpg|800px]] 

==Testing==

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

For testing purposes, we are using the 'expertiza.debugging@gmail.com' as both author and reviewer.
There are two views that need to be tested manually.

1. Author View:

The author must follow the following steps:
1. Go to the Assignments page.
2. Click on the link which is placed on the right corner of the page called "send email to reviewers".
3. On clicking the above link, the author must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

2. Reviewer View:

The reviewer must follow the following steps:
1. Go to the other's work page.
2. Click on the link which is placed on the right corner of the page called "send email to author".
3. On clicking the above link, the reviewer must be redirected to a page with an email text box.
4. Type the email message and click on send.
5. Log in to the email to check if the message is received.

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

== Team Members ==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:33:57Z

Sdamulu:

==Introduction==

===Expertiza Background ===
Expertiza is a web application where students can submit and peer-review learning objects (articles, codes, websites, etc). Instructors add and grade the assignments submitted by students to Expertiza. Students can be assigned in teams based on their selection of the topics. It has functionalities such as peer reviews in which students can provide feedback on other's work which helps peer in better developing the project. It is supported by the National Science Foundation.

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Proposed Changes==

As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|500px]] 
[[File:Message-to-R.png|500px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|500px]] 
[[File:Msg-to-A.png|500px]] 

===Flowchart===

'''The flow for authors to email reviewers regarding the work they have reviewed is as below:'''

[[File:Author's view flowchart.jpg|800px]] 

'''The flow for reviewers to email authors whose work they have reviewed:'''

[[File:Reviewers_View_Flowchart.jpg|800px]] 

==Testing==

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

== Team Members ==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:32:52Z

Sdamulu: /* Proposed Changes */

==Introduction==

===Expertiza Background ===
Expertiza is a web application where students can submit and peer-review learning objects (articles, codes, websites, etc). Instructors add and grade the assignments submitted by students to Expertiza. Students can be assigned in teams based on their selection of the topics. It has functionalities such as peer reviews in which students can provide feedback on other's work which helps peer in better developing the project. It is supported by the National Science Foundation.

=== Problem Statement ===

This project adds a new feature which will enable a reviewer to send an Email to authors from inside Expertiza or for the author to email all those reviewing them. Often when reviewing another team’s submissions, a reviewer might notice that their deployment link is broken or there is some other issue. Currently, there is no way to email the authors. This features is proposed to solve this issue.

==Scope of the Feature==

- The feature allows authors to send a common Email to all the reviewers to report any issues or updates to their project to be reviewed. 
- It can allow a reviewer to send an email to a particular author if the reviewer wants to convey any issues found with that particular project. 
- Reviewers will be anonymous to authors. 

==Proposed Changes==

As depicted below, Authors will be given a link on their main Assignment page “Send Email to Reviewers” which will take them to a new page where they are given a text box for typing and sending an email to all their reviewers. 

[[File:Email-R.png|500px]] 
[[File:Message-to-R.png|500px]] 

Reviewers will be given a similar text box link on their “Other’s Work” page next to each review that they are doing. 

[[File:Email-to-A.png|500px]] 
[[File:Msg-to-A.png|500px]] 

===Flowchart===

[[File:Author's view flowchart.jpg|800px]] 

[[File:Reviewers_View_Flowchart.jpg|800px]] 

==Testing==

Since this is a new Feature, Rspec test cases will be added for all the new methods introduced in the MailHelper class method.

===Manual Testing===

==Design Pattern==

A design pattern is a general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations.

We will be implementing the decorator design pattern in our code. The decorator pattern is used to add/extend existing functionality without modifying the existing code. Our code is also going to follow the open-closed principle.

==References==

== Team Members ==

Ashritha Bommagani (abommag@ncsu.edu)

Abhishek (aaupadhy@ncsu.edu)

Harini Bharata (hbharat@ncsu.edu)

Sri Pallavi Damuluri (sdamulu@ncsu.edu)

File:Msg-to-A.png

2022-04-04T21:32:35Z

Sdamulu:

File:Message-to-R.png

2022-04-04T21:31:54Z

Sdamulu:

File:Email-to-A.png

2022-04-04T21:30:56Z

Sdamulu:

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:27:50Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:26:25Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:25:08Z

Sdamulu: /* Proposed Changes */

File:Textbox-R.png

2022-04-04T21:24:33Z

Sdamulu:

File:Textbox-A.png

2022-04-04T21:23:36Z

Sdamulu:

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:23:03Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:22:31Z

Sdamulu: /* Proposed Changes */

File:Email-R.png

2022-04-04T21:22:16Z

Sdamulu:

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:21:52Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:21:21Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:20:43Z

Sdamulu: /* Proposed Changes */

File:Email-A.png

2022-04-04T21:20:02Z

Sdamulu:

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:17:07Z

Sdamulu: /* Testing */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:08:57Z

Sdamulu: /* Design Pattern */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:03:10Z

Sdamulu:

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:02:25Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:02:02Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:01:49Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:00:58Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T21:00:21Z

Sdamulu: /* Proposed Changes */

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T20:51:45Z

Sdamulu: /* Proposed Changes */

File:View4.png

2022-04-04T20:51:16Z

Sdamulu:

File:View3.png

2022-04-04T20:49:48Z

Sdamulu:

File:View2.png

2022-04-04T20:48:17Z

Sdamulu: Sdamulu uploaded a new version of File:View2.png

File:View1.png

2022-04-04T20:47:40Z

Sdamulu:

CSC/ECE 517 Spring 2022 - E2246: Email your authors/reviewers, with complete tests

2022-04-04T20:45:09Z

Sdamulu: /* Scope of the Feature */