Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-11T20:49:03Z

Pmukher: /* Use Case Diagram */

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza Expertiza's Github Site]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> and Capybara<ref>[https://github.com/jnicklas/capybara]</ref> using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref>. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
===RSpec===

Rspec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> is Behavior Driven Development<ref>[https://en.wikipedia.org/wiki/Behavior-driven_development Behavior Driven Development]</ref> framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber<ref>[https://cucumber.io/ Cucumber]</ref>. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

===Capybara===

Capybara<ref>[https://github.com/jnicklas/capybara Capybara github link]</ref> is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

===Integration Testing===

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested<ref>[https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx Integration Testing - Microsoft Developer Network]</ref>. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up<ref>[https://en.wikipedia.org/wiki/Integration_testing Integration Testing - Wikipedia]</ref>.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Pattern and Approach==

We are required to write integration tests for the peer review process. Since we are not adding any new functionalities or amending any existing ones we don’t need to follow any specific design pattern. However we need to follow a specific integration testing approach to conduct the integration testing. The testing approach that we have decided to follow is '''Top-Down'''.
We are first going to create the following entities
* '''User or Reviewer'''
* '''Assignment Questionnaire or Rubric'''
* '''Assignment'''
Then we plan to incrementally test the interaction of these entities in a bottom-up manner.
We first test whether the user is able to successfully login.
If he is able to successfully login, we test whether he is able to successfully select an assignment for review.
If he is able to successfully select an assignment, we test whether he is able to able to submit a review successfully based on whether it is a text-based, point-based or both and whether he chooses to answer all, some or none of the questions of the rubric.

==Flowchart for the Peer Review Testing Approach==
[[File:FlowchartE1591 2.png]]

==Use Case Diagram==

[[File: UseCaseE1591.png]]

==Test Plan==
The following section describes how we plan on testing the application based requirements found on the Project Description<ref>[https://docs.google.com/document/d/1t0keeNQ2kP0NmcgIrtQXGi5K_GhQYcKzEVWJPPRBOHE/edit Project Description]</ref>. We wish to create Integration tests that thoroughly test a Student user reviewing an assignment submission.

=== Test Cases Prerequisites ===
To create and run our test cases we require some setup in Expertiza. The following list describes the information that we will enter into the system before running any of our test cases.

# We will use the Student with the username 'student13' and password 'password' to login as a Student.
# We will enroll Student into a specific course.
# We will create an Assignment per individual test case that is customized for our test case.
# We will submit an Assignment from a student other than 'student13' for 'student13' to review

=== Test Cases ===
The following list describes the individual test cases we will creating for Expertiza.

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

File:UseCaseE1591.png

2015-11-11T20:47:46Z

Pmukher: uploaded a new version of "File:UseCaseE1591.png"

File:UseCaseE1591.png

2015-11-11T20:47:35Z

Pmukher:

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-11T20:47:06Z

Pmukher:

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza Expertiza's Github Site]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> and Capybara<ref>[https://github.com/jnicklas/capybara]</ref> using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref>. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
===RSpec===

Rspec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> is Behavior Driven Development<ref>[https://en.wikipedia.org/wiki/Behavior-driven_development Behavior Driven Development]</ref> framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber<ref>[https://cucumber.io/ Cucumber]</ref>. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

===Capybara===

Capybara<ref>[https://github.com/jnicklas/capybara Capybara github link]</ref> is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

===Integration Testing===

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested<ref>[https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx Integration Testing - Microsoft Developer Network]</ref>. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up<ref>[https://en.wikipedia.org/wiki/Integration_testing Integration Testing - Wikipedia]</ref>.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Pattern and Approach==

We are required to write integration tests for the peer review process. Since we are not adding any new functionalities or amending any existing ones we don’t need to follow any specific design pattern. However we need to follow a specific integration testing approach to conduct the integration testing. The testing approach that we have decided to follow is '''Top-Down'''.
We are first going to create the following entities
* '''User or Reviewer'''
* '''Assignment Questionnaire or Rubric'''
* '''Assignment'''
Then we plan to incrementally test the interaction of these entities in a bottom-up manner.
We first test whether the user is able to successfully login.
If he is able to successfully login, we test whether he is able to successfully select an assignment for review.
If he is able to successfully select an assignment, we test whether he is able to able to submit a review successfully based on whether it is a text-based, point-based or both and whether he chooses to answer all, some or none of the questions of the rubric.

==Flowchart for the Peer Review Testing Approach==
[[File:FlowchartE1591 2.png]]

==Use Case Diagram==

[[File:Example.jpg]]

==Test Plan==
The following section describes how we plan on testing the application based requirements found on the Project Description<ref>[https://docs.google.com/document/d/1t0keeNQ2kP0NmcgIrtQXGi5K_GhQYcKzEVWJPPRBOHE/edit Project Description]</ref>. We wish to create Integration tests that thoroughly test a Student user reviewing an assignment submission.

=== Test Cases Prerequisites ===
To create and run our test cases we require some setup in Expertiza. The following list describes the information that we will enter into the system before running any of our test cases.

# We will use the Student with the username 'student13' and password 'password' to login as a Student.
# We will enroll Student into a specific course.
# We will create an Assignment per individual test case that is customized for our test case.
# We will submit an Assignment from a student other than 'student13' for 'student13' to review

=== Test Cases ===
The following list describes the individual test cases we will creating for Expertiza.

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-11T19:34:32Z

Pmukher:

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza Expertiza's Github Site]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> and Capybara<ref>[https://github.com/jnicklas/capybara]</ref> using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref>. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
===RSpec===

Rspec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> is Behavior Driven Development<ref>[https://en.wikipedia.org/wiki/Behavior-driven_development Behavior Driven Development]</ref> framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber<ref>[https://cucumber.io/ Cucumber]</ref>. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

===Capybara===

Capybara<ref>[https://github.com/jnicklas/capybara Capybara github link]</ref> is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

===Integration Testing===

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested<ref>[https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx Integration Testing - Microsoft Developer Network]</ref>. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up<ref>[https://en.wikipedia.org/wiki/Integration_testing Integration Testing - Wikipedia]</ref>.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Pattern and Approach==

We are required to write integration tests for the peer review process. Since we are not adding any new functionalities or amending any existing ones we don’t need to follow any specific design pattern. However we need to follow a specific integration testing approach to conduct the integration testing. The testing approach that we have decided to follow is '''Top-Down'''.
We are first going to create the following entities
* '''User or Reviewer'''
* '''Assignment Questionnaire or Rubric'''
* '''Assignment'''
Then we plan to incrementally test the interaction of these entities in a bottom-up manner.
We first test whether the user is able to successfully login.
If he is able to successfully login, we test whether he is able to successfully select an assignment for review.
If he is able to successfully select an assignment, we test whether he is able to able to submit a review successfully based on whether it is a text-based, point-based or both and whether he chooses to answer all, some or none of the questions of the rubric.

==Flowchart for the Peer Review Testing Approach==
[[File:FlowchartE1591 2.png]]

==Test Plan==
The following section describes how we plan on testing the application based requirements found on the Project Description<ref>[https://docs.google.com/document/d/1t0keeNQ2kP0NmcgIrtQXGi5K_GhQYcKzEVWJPPRBOHE/edit Project Description]</ref>. We wish to create Integration tests that thoroughly test a Student user reviewing an assignment submission.

=== Test Cases Prerequisites ===
To create and run our test cases we require some setup in Expertiza. The following list describes the information that we will enter into the system before running any of our test cases.

# We will use the Student with the username 'student13' and password 'password' to login as a Student.
# We will enroll Student into a specific course.
# We will create an Assignment per individual test case that is customized for our test case.
# We will submit an Assignment from a student other than 'student13' for 'student13' to review

=== Test Cases ===
The following list describes the individual test cases we will creating for Expertiza.

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-11T19:32:29Z

Pmukher:

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza Expertiza's Github Site]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> and Capybara<ref>[https://github.com/jnicklas/capybara]</ref> using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref>. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
===RSpec===

Rspec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> is Behavior Driven Development<ref>[https://en.wikipedia.org/wiki/Behavior-driven_development Behavior Driven Development]</ref> framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber<ref>[https://cucumber.io/ Cucumber]</ref>. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

===Capybara===

Capybara<ref>[https://github.com/jnicklas/capybara Capybara github link]</ref> is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

===Integration Testing===

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested<ref>[https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx Integration Testing - Microsoft Developer Network]</ref>. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up<ref>[https://en.wikipedia.org/wiki/Integration_testing Integration Testing - Wikipedia]</ref>.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Pattern and Approach==

We are required to write integration tests for the peer review process. Since we are not adding any new functionalities or amending any existing ones we don’t need to follow any specific design pattern. However we need to follow a specific integration testing approach to conduct the integration testing. The testing approach that we have decided to follow is '''Top-Down'''.
We are first going to create the following entities
* '''User or Reviewer'''
* '''Assignment Questionnaire or Rubric'''
* '''Assignment'''
Then we plan to incrementally test the interaction of these entities in a bottom-up manner.
We first test whether the user is able to successfully login.
If he is able to successfully login, we test whether he is able to successfully select an assignment for review.
If he is able to successfully select an assignment, we test whether he is able to able to submit a review successfully based on whether it is a text-based, point-based or both and whether he chooses to answer all, some or none of the questions of the rubric.

==Test Plan==
The following section describes how we plan on testing the application based requirements found on the Project Description<ref>[https://docs.google.com/document/d/1t0keeNQ2kP0NmcgIrtQXGi5K_GhQYcKzEVWJPPRBOHE/edit Project Description]</ref>. We wish to create Integration tests that thoroughly test a Student user reviewing an assignment submission.

=== Test Cases Prerequisites ===
To create and run our test cases we require some setup in Expertiza. The following list describes the information that we will enter into the system before running any of our test cases.

# We will use the Student with the username 'student13' and password 'password' to login as a Student.
# We will enroll Student into a specific course.
# We will create an Assignment per individual test case that is customized for our test case.
# We will submit an Assignment from a student other than 'student13' for 'student13' to review

=== Test Cases ===
The following list describes the individual test cases we will creating for Expertiza.

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

File:FlowchartE1591 2.png

2015-11-11T19:31:09Z

Pmukher: uploaded a new version of "File:FlowchartE1591 2.png"

File:FlowchartE1591 2.png

2015-11-11T19:29:24Z

Pmukher:

File:FlowchartE1591.png

2015-11-11T19:26:41Z

Pmukher: uploaded a new version of "File:FlowchartE1591.png"

File:FlowchartE1591.png

2015-11-11T19:25:41Z

Pmukher:

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-11T19:22:45Z

Pmukher:

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza Expertiza's Github Site]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> and Capybara<ref>[https://github.com/jnicklas/capybara]</ref> using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref>. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
===RSpec===

Rspec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> is Behavior Driven Development<ref>[https://en.wikipedia.org/wiki/Behavior-driven_development Behavior Driven Development]</ref> framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber<ref>[https://cucumber.io/ Cucumber]</ref>. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

===Capybara===

Capybara<ref>[https://github.com/jnicklas/capybara Capybara github link]</ref> is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

===Integration Testing===

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested<ref>[https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx Integration Testing - Microsoft Developer Network]</ref>. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up<ref>[https://en.wikipedia.org/wiki/Integration_testing Integration Testing - Wikipedia]</ref>.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Pattern and Approach==

We are required to write integration tests for the peer review process. Since we are not adding any new functionalities or amending any existing ones we don’t need to follow any specific design pattern. However we need to follow a specific integration testing approach to conduct the integration testing. The testing approach that we have decided to follow is '''Top-Down'''.
We are first going to create the following entities
* '''User or Reviewer'''
* '''Assignment Questionnaire or Rubric'''
* '''Assignment'''
Then we plan to incrementally test the interaction of these entities in a bottom-up manner.
We first test whether the user is able to successfully login.
If he is able to successfully login, we test whether he is able to successfully select an assignment for review.
If he is able to successfully select an assignment, we test whether he is able to able to submit a review successfully based on whether it is a text-based, point-based or both and whether he chooses to answer all, some or none of the questions of the rubric.

==Flowchart of the Peer Review Testing Process==

[[File:Example.jpg]]

==Test Plan==
The following section describes how we plan on testing the application based requirements found on the Project Description<ref>[https://docs.google.com/document/d/1t0keeNQ2kP0NmcgIrtQXGi5K_GhQYcKzEVWJPPRBOHE/edit Project Description]</ref>. We wish to create Integration tests that thoroughly test a Student user reviewing an assignment submission.

=== Test Cases Prerequisites ===
To create and run our test cases we require some setup in Expertiza. The following list describes the information that we will enter into the system before running any of our test cases.

# We will use the Student with the username 'student13' and password 'password' to login as a Student.
# We will enroll Student into a specific course.
# We will create an Assignment per individual test case that is customized for our test case.
# We will submit an Assignment from a student other than 'student13' for 'student13' to review

=== Test Cases ===
The following list describes the individual test cases we will creating for Expertiza.

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

File:Flowchart of the Peer Review Testing Process.png

2015-11-11T19:03:53Z

Pmukher: uploaded a new version of "File:Flowchart of the Peer Review Testing Process.png"

File:Flowchart of the Peer Review Testing Process.png

2015-11-11T19:03:12Z

Pmukher:

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-11T17:46:52Z

Pmukher:

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza Expertiza's Github Site]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> and Capybara<ref>[https://github.com/jnicklas/capybara]</ref> using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref>. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
===RSpec===

Rspec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> is Behavior Driven Development<ref>[https://en.wikipedia.org/wiki/Behavior-driven_development Behavior Driven Development]</ref> framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber<ref>[https://cucumber.io/ Cucumber]</ref>. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

===Capybara===

Capybara<ref>[https://github.com/jnicklas/capybara Capybara github link]</ref> is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

===Integration Testing===

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested<ref>[https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx Integration Testing - Microsoft Developer Network]</ref>. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up<ref>[https://en.wikipedia.org/wiki/Integration_testing Integration Testing - Wikipedia]</ref>.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Pattern and Approach==

Test Pattern and Approach

We are required to write integration tests for the peer review process. Since we are not adding any new functionalities or amending any existing ones we don’t need to follow any specific design pattern. However we need to follow a specific integration testing approach to conduct the integration testing. The testing approach that we have decided to follow is '''Top-Down'''.
We are first going to create the following entities
* '''User or Reviewer'''
* '''Assignment Questionnaire or Rubric'''
* '''Assignment'''
Then we plan to incrementally test the interaction of these entities in a bottom-up manner.
We first test whether the user is able to successfully login.
If he is able to successfully login, we test whether he is able to successfully select an assignment for review.
If he is able to successfully select an assignment, we test whether he is able to able to submit a review successfully based on whether it is a text-based, point-based or both and whether he chooses to answer all, some or none of the questions of the rubric.

==Test Plan==
The following section describes how we plan on testing the application based requirements found on the Project Description<ref>[https://docs.google.com/document/d/1t0keeNQ2kP0NmcgIrtQXGi5K_GhQYcKzEVWJPPRBOHE/edit Project Description]</ref>. We wish to create Integration tests that thoroughly test a Student user reviewing an assignment submission.

=== Test Cases Prerequisites ===
To create and run our test cases we require some setup in Expertiza. The following list describes the information that we will enter into the system before running any of our test cases.

# We will use the Student with the username 'student13' and password 'password' to login as a Student.
# We will enroll Student into a specific course.
# We will create an Assignment per individual test case that is customized for our test case.
# We will submit an Assignment from a student other than 'student13' for 'student13' to review

=== Test Cases ===
The following list describes the individual test cases we will creating for Expertiza.

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-07T19:32:06Z

Pmukher: /* Purpose */

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza Expertiza's Github Site]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> and Capybara<ref>[https://github.com/jnicklas/capybara]</ref> using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref>. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
===RSpec===

Rspec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> is Behavior Driven Development<ref>[https://en.wikipedia.org/wiki/Behavior-driven_development Behavior Driven Development]</ref> framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber<ref>[https://cucumber.io/ Cucumber]</ref>. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

===Capybara===

Capybara<ref>[https://github.com/jnicklas/capybara Capybara github link]</ref> is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

===Integration Testing===

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested<ref>[https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx Integration Testing - Microsoft Developer Network]</ref>. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up<ref>[https://en.wikipedia.org/wiki/Integration_testing Integration Testing - Wikipedia]</ref>.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Scenarios==
Using the testing requirements found on the Project Description<ref>[https://docs.google.com/document/d/1t0keeNQ2kP0NmcgIrtQXGi5K_GhQYcKzEVWJPPRBOHE/edit Project Description]</ref>:

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-07T19:27:09Z

Pmukher: /* Purpose */

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza Expertiza's Github Site]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> and Capybara using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref>. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
===RSpec===

Rspec<ref>[http://rspec.info/documentation/ Rspec].''Rspec Documentation''</ref> is Behavior Driven Development<ref>[https://en.wikipedia.org/wiki/Behavior-driven_development Behavior Driven Development]</ref> framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like <ref>Cucumber</ref>. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

===Capybara===

Capybara<ref>[https://github.com/jnicklas/capybara Capybara github link]</ref> is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

===Integration Testing===

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested<ref>[https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx https://msdn.microsoft.com/en-us/library/aa292128(v=vs.71).aspx]</ref>. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up<ref>[https://en.wikipedia.org/wiki/Integration_testing https://en.wikipedia.org/wiki/Integration_testing]</ref>.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Scenarios==
Using the testing requirements found on the Project Description:

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-07T19:17:30Z

Pmukher: /* Purpose */

==Background==
Expertiza<ref>[https://github.com/expertiza/expertiza]</ref> is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re-submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are and Capybara using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec. The various entities like users, assignment, questionnaire and instructor will be simulated using Capybara.

==Technologies to be used==
'''RSpec'''

Rspec is Behavior Driven Development framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

'''Capybara'''

Capybara is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

'''Integration Testing'''

Integration testing is a phase of software testing where units which have already been tested are combined into a component and the interface between them is tested. The idea is to test combination of pieces and eventually expand the process to test the modules with those of the other group. Eventually, all the modules making up a process are tested together.
Integration testing identifies the problem that occurs when units are combined. Some different types of integration testing are big bang, top- down, bottom-up.
*Big Bang Integration Testing – All modules are integrated simultaneously, after which everything is tested as a whole. It is very effective for saving time in the integration testing process.
*The top down approach – The highest level modules are tested first. This allows high level logic and data flow to be integrated early in the process.
*The bottom up approach - In this approach, lowest level components are tested first, and then used to facilitate the testing of higher level components.

==Test Scenarios==
Using the testing requirements found on the Project Description:

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==
<references></references>

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-07T19:10:55Z

Pmukher: /* Purpose */

==Background==

Expertiza is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.

One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called "Other’s Work" where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link.

After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.

For some assignments there is a scope for a re submission of an improved version of the work. After such a re submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

==Purpose==
The purpose of the project is to perform an integration testing for the peer review of a submitted assignment. We aim to write test cases that test the different positive test scenarios for which the reviewer should be able to successfully submit the review to an assignment. The review process has certain minimum guidelines which need to be adhered to. We also plan to test the negative scenarios for which the reviewer doesn’t adhere to these guidelines and hence should not be able to submit the review to the assignment.
The Expertiza project has been developed using Ruby on Rails. The technologies to be used for the project are '''RSpec''' and '''Capybara''' using Ruby on Rails as an underlying framework. We will write the spec methods using RSpec. The various entities like '''users, assignment''' '''questionnaire''' and '''instructor''' will be simulated using Capybara.

==Technologies to be used==
'''RSpec'''

Rspec is Behavior Driven Development framework for ruby, it is a meta gem composed of different libraries designed to work together or with other testing tools like Cucumber. It has dependencies on Rspec core, Rspec expectations, Rspec mocks gems which can be loaded by using 'require'.

Installation-
gem install rspec

'''Capybara'''

Capybara is a library written in ruby, it helps you to test your web applications by pretending to be a user and following the user story, it simulates the browser to interact with app to receive pages parse the HTML and submit forms just as an actual user would do. Capybara can interact with many different drivers which execute tests through the same clean and simple interface. One can seamlessly choose between Selenium, Webkit or pure Ruby drivers.

Installation-

Capybara requires ruby 1.9.3 or later,to install add following line to your gem file and run bundle install
gem 'capybara'
If testing a rails app add this to your test helper file
require 'capybara/rails'

==Test Scenarios==
Using the testing requirements found on the Project Description:

T1: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will successfully submit the review answering the points based review choices.

T2: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by only answering some of the points based review choices.

T3: Login as a Student user and select a submission for review. The submission will only contain points based review choices. The user will unsuccessfully submit the review by answering none of the points based review choices.

T4: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will successfully submit the review answering the text based review choices.

T5: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by only answering some of the text based review choices.

T6: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will unsuccessfully submit the review by answering none of the text based review choices.

T7: Login as a Student user and select a submission for review. The submission will only contain text based review choices. The user will submit the review by answering all of the text based review choices with single word answers.

T8: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will successfully submit the review answering all of the review choices.

T9: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering only some of the review choices.

T10: Login as a Student user and select a submission for review. The submission will only contain both points based and text based review choices. The user will unsuccessfully submit the review answering none of the review choices.

==References==

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-07T18:29:41Z

Pmukher:

CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review

2015-11-07T18:26:33Z

Pmukher: Created page with "Integration Testing for Review Reviewing is major portion of expertiza. The main task of the project is to write integration tests scenario for reviewing a assignment submission...."

Integration Testing for Review
Reviewing is major portion of expertiza. The main task of the project is to write integration tests scenario for reviewing a assignment submission.
User. instructor, AssignmentQuestionaire these
The testing scenario will consists of
1. Login as student
2. Select submission for review.
3. Submit reviews with multiple scenarios like only points, only comments, single word comment,
Test the above scenario with multiple Assignment Questionnaire.

Background

Expertiza is an open-source web tool that is used for online assignment completion purpose for different courses. The software enables the students to form online teams and choose different assignment topics. Each topic has a completion deadline and the students can submit the links to their work or assignments through expertiza.
One of the key features of expertiza is the online peer review process. Students who are enrolled in the same courses can review the works or the assignments of the fellow students. Typically for each assignment there is a link called Other’s Work where a student is prompted to give feedback to the works of their fellow classmates. This link becomes active after a certain date that is determined by the instructor or the administrator. After the date, a student can choose one of the assignments that are available for review through the activated link. After an assignment has been chosen for review, the reviewer will be presented with a review sheet that has a number of parameters based upon which the review should be done. The reviewer chooses a rating for each parameter, typically being the lowest and 5 as the highest. He can also leave a comment justifying his rating and stating the scopes of improvements for the project. The team members whose assignment has been reviewed can also review the review, i.e. provide an explanation about their work or give comments with respect to the feedback provided by the reviewer.
For some assignments there is a scope for a re submission of an improved version of the work. After such a re submission the reviewer can again review the assignment editing and updating his previous review based upon the resubmitted work.

Purpose
Once an The project aims to write integration tests for the
Technologies to be used
Test Scenarios
References

CSC/ECE 517 Fall 2015

2015-11-07T18:25:19Z

Pmukher:

==Writing Assignment 2==
*[[CSC/ECE_517_Fall_2015/sample_page]]
*[[CSC/ECE_517_Fall_2015/ossE1558BGJ]]
*[[CSC/ECE 517 Fall 2015/oss/M1502/AAAASS]]
*[[CSC/ECE 517 Fall 2015/oss/M1503/IntegrateXMLParser]]
*[[CSC/ECE_517_Fall_2015/ossE1568BZHXJS]]
*[[CSC/ECE_517_Fall_2015/ossE1572VGA]]
*[[CSC/ECE_517_Fall_2015/oss_E1573_sap]]
*[[CSC/ECE 517 Fall 2015/oss E1559 rrz]]
*[[CSC/ECE 517 Fall 2015/oss E1570 avr]]
*[[CSC/ECE 517 Fall 2015/oss E1556 CHM]]
*[[CSC/ECE 517 Fall 2015/oss M1504 JJD]]
*[[CSC/ECE 517 Fall 2015/oss E1562 APS]]
*[[CSC/ECE 517 Fall 2015/oss M1501 GSN]]
*[[CSC/ECE 517 Fall 2015/oss M1501 GSN]]
*[[CSC/ECE 517 Fall 2015/oss E1550 KMM]]
*[[CSC/ECE 517 Fall 2015/oss E1551 RGS]]
*[[CSC/ECE 517 Fall 2015/oss E1555 GMR]]
*[[CSC/ECE 517 Fall 2015/oss E1552 NFR]]
*[[CSC/ECE 517 Fall 2015/oss E1565 AAJ]]
*[[CSC/ECE 517 Fall 2015/oss E1561 WZL]]
*[[CSC/ECE 517 Fall 2015/oss E1553 AAJ]]
*[[CSC/ECE 517 Fall 2015/oss E1554 AAR]]
*[[CSC/ECE 517 Fall 2015/oss E1569 JNR]]
*[[CSC/ECE 517 Fall 2015/oss E1560 PSV]]
*[[CSC/ECE 517 Fall 2015/oss M1505 MSV]]
*[[CSC/ECE 517 Fall 2015/oss E1557 GXM]]
*[[CSC/ECE 517 Fall 2015/oss E1566 ARB]]
*[[CSC/ECE 517 Fall 2015/oss E1567 APT]]
*[[CSC/ECE 517 Fall 2015/oss E1574 BKS]]
*[[CSC/ECE 517 Fall 2015/ossA1550RAN]]
*[[CSC/ECE 517 Fall 2015/oss E1571]]

==Final Project Design Document==
*[[CSC/ECE 517 Fall 2015 E1577 MayYellowRoverJump]]
*[[CSC/ECE 517 Fall 2015 E1586 AnonymousChatBetweenAuthorAndReviewer]]
*[[CSC/ECE 517 Fall 2015 E1582 Create integration tests for the instructor interface using capybara and rspec]]
*[[CSC/ECE 517 Fall 2015 E1576 Refactoring submitted content (hyperlinks and files)]]
*[[CSC/ECE 517 Fall 2015 E1590 Integration testing for Team creation]]
*[[CSC/ECE 517 Fall 2015 E1585 Use Ajax for Add Participants, Add TA ,Edit Questionnaires Screens]]
*[[CSC/ECE 517 Fall 2015 E1581 Integration testing for student interface]]
*[[CSC/ECE 517 Fall 2015 E1583 Fix the CSS used for Menu Item]]
*[[CSC/ECE 517 Fall 2015 E1591 Integration testing for peer review]]

CSC/ECE 517 Fall 2015/oss E1573 sap

2015-10-30T18:04:12Z

Pmukher:

== '''E1573 Unit Test for Assignment model''' ==

Assignment.rb is a model in Expertiza -a ruby rails application, that handles the various assignments assigned by the instructors to the teams during their coursework. The OSS project "Unit Test for Assignment model" tests the relationships, validation and scope of the assignment model using RSpec and Factory Girl.

==Why is unit testing required==
*Visibility and reporting
*Control and correction
*Efficiency and speed
*Planning and predictability
*Customer satisfaction

==Goals==
*Write specs for major instance methods of assignment.rb model
*Create test data by writing factories and use the test data to test the model with rspec

==Tested Spec Methods==

'''team_Assignment''': The methods returns true by default indicating it is a team assignment. The rspec method '''#team_assignment''' checks whether the method returns true or not

'''has_Teams''': The method in the assignment model returns true or false depending upon whether the assignement has one or more teams associated with it. The corresponding rspec method '''#has_teams?''' checks whether the method returns true when a team has been assigned to it.

'''has_Topics''': The method in the assignment model returns true or false depending upon whether the assignment has one or more topics associated with it. The corresponding rspec method '''#has_topics'''? checks whether the method returns true when a team has been assigned to it.

'''is_wiki_assignment''': The method in the assignment model returns true or false depending upon whether the assignment is a wiki assignment or not. It returns true if its '''wiki_type_id > 1'''. The corresponding rspec method '''#is_wiki_assignment''' validates that the model method returns true when the assignment is a wiki assignment with wiki_type_id >1

'''is_google_doc''': The method in the assignment model returns true or false depending upon whether the assignment is a google document or not. It returns true if its '''wiki_type_id =4'''. The corresponding rspec method #is_google_doc validates that the model method returns true when the assignment is a google document with wiki_type_id =4

is_microtask: The method in the assignment model returns true or false depending upon whether the assignment is a microtask or not. It returns true if the microtask variable isassigned true in the assignment. The corresponding rspec method '''#is_microtask?''' validates that the model method returns true when the microtask variable is assigned true in the assignment

'''dynamic_reviewer_assignment''': The method in the assignment model checks whether the '''review_assignment_strategy''' is set to ''''Auto-Selected'''' or not. It returns true if the review_assignment_strategy value is set to ‘Auto-Selected’. The corresponding rspec method '''#dynamic_reviewer_assignment?''' validates that the model method returns true when the review_assignment_strategy is set to 'Auto-Selected'.

'''candidate_assignment_teams_to_review''': The spec method '''#candidate_assignment_teams_to_review''' validates whether the model method returns nil when there are no contributors to the assignment in the team

'''candidate_topics_for_quiz''': The corresponding spec method validates whether the model method returns nil if the assignment has no sign up topic

==Factory Girl==
Factory Girl is a fixture replacement which has easy-to-use definition syntax. <ref>http://www.rubydoc.info/gems/factory_girl/file/README.md</ref>factory_girl_rails provided Rails integration for Factory Girl. We define a factory to create objects which will be used for testing.
==RSpec==
RSpec is used for Test Driven Development. It is a Domain Specific Language, also called DSL, used specifically for Ruby Rails projects. It is used for describing the expected behavior of a system with executable examples. RSpec code is similar to Ruby code and it leverages Ruby features and syntax so as to make up a “mini-language” focused on the job of testing. It is commonly used for Unit Testing and Functional testing.<ref>https://www.youtube.com/watch?v=oFX1KPNRruA&feature=relmfu</ref>

== Setting up Rspec and FactoryGirl ==

=== GemFile ===
Add the following lines of code in the gemfile:
<code><nowiki>source 'https://rubygems.org'</nowiki>

gem 'rspec-rails','~>3.0'
gem 'factory_girl-rails','~>4.0'</code>

=== Preparing FactoryGirl ===
FactoryGirl is a Ruby Gem that mocks certain classes for
automated tests. We will use FactoryGirl to mock nodes and
lists.

Add the following lines of code to the RSpec config in spec/spec_helper.rb.
<code>require 'factory_girl_rails'

RSpec.configure do |config|
config.include FactoryGirl::Syntax::Methods
end</code>

=== Building Factories ===
Each factory has a name and a set of attributes. Implicitly, the name of the factory corresponds to the the class, whose test objects are created by default, but it's possible to explicitly specify the class also.

This will create the objects of the User class:
factory :user do
    sequence(:name) { |n| "NewName #{n}" }
    fullname {"test_user"}
    email {"sjolly@ncsu.edu"}
    parent_id =1
    is_new_user=true
end
This will use the User class (Admin would have been created):
factory :admin '''class: User''' do
sequence(:name) { |n| "NewName #{n}" }
fullname {"test_user"}
email {"sjolly@ncsu.edu"}
parent_id =1
is_new_user=true
end

It's possible to set up associations within factories. If the factory name is the same as the association name, the factory name can be left out, as given below :

Factory for Assignment having associations with instructor and wiki_type:

factory :assignment_without_name, class: Assignment do
name {}
submitter_count {3}
is_coding_assignment {true}
microtask {true}
review_assignment_strategy {'Auto-Selected'}
'''''association :instructor, factory: :user'''''
'''association :wiki_type, factory: :wiki_typ'''e''
end

===Creating specs ===

*Create a assignment_spec.rb file in spec/models folder

An example of a test case is
<code>require 'spec_helper'

describe "Team_Assignment" do
it "checks team assignment should be true" do
assign=FactoryGirl.create(:assignment)
res=assign.team_assignment
expect(res).to be true
end</code>

===Running RSpec===

$ rspec spec/models/assignment_spec.rb
You should be able to run tests successfully and see the following message:
Finished in 1.11 seconds (files took 14.47 seconds to load)
14 examples, 0 failures

==References==
<References/>

CSC/ECE 517 Fall 2015/oss E1573 sap

2015-10-30T16:18:26Z

Pmukher:

== '''E1573 Unit Test for Assignment model''' ==

Assignment.rb is a model in Expertiza -a ruby rails application, that handles the various assignments assigned by the instructors to the teams during their coursework. The OSS project "Unit Test for Assignment model" tests the relationships, validation and scope of the assignment model using RSpec and Factory Girl.

==Goals==
*Write specs for major instance methods of assignment.rb model
*Create test data by writing factories and use the test data to test the model with rspec

==Why is unit testing required==
*Visibility and reporting
*Control and correction
*Efficiency and speed
*Planning and predictability
*Customer satisfaction

==Factory Girl==
Factory Girl is a fixture replacement which has easy-to-use definition syntax. <ref>http://www.rubydoc.info/gems/factory_girl/file/README.md</ref>factory_girl_rails provided Rails integration for Factory Girl. We define a factory to create objects which will be used for testing.
==RSpec==
RSpec is used for Test Driven Development. It is a Domain Specific Language, also called DSL, used specifically for Ruby Rails projects. It is used for describing the expected behavior of a system with executable examples. RSpec code is similar to Ruby code and it leverages Ruby features and syntax so as to make up a “mini-language” focused on the job of testing. It is commonly used for Unit Testing and Functional testing.<ref>https://www.youtube.com/watch?v=oFX1KPNRruA&feature=relmfu</ref>

== Setting up Rspec and FactoryGirl ==

=== GemFile ===
Add the following lines of code in the gemfile:
<code><nowiki>source 'https://rubygems.org'</nowiki>

gem 'rspec-rails','~>3.0'
gem 'factory_girl-rails','~>4.0'</code>

=== Preparing FactoryGirl ===
FactoryGirl is a Ruby Gem that mocks certain classes for
automated tests. We will use FactoryGirl to mock nodes and
lists.

Add the following lines of code to the RSpec config in spec/spec_helper.rb.
<code>require 'factory_girl_rails'

RSpec.configure do |config|
config.include FactoryGirl::Syntax::Methods
end</code>

=== Building Factories ===
Each factory has a name and a set of attributes. Implicitly, the name of the factory corresponds to the the class, whose test objects are created by default, but it's possible to explicitly specify the class also.

This will create the objects of the User class:
factory :user do
    sequence(:name) { |n| "NewName #{n}" }
    fullname {"test_user"}
    email {"sjolly@ncsu.edu"}
    parent_id =1
    is_new_user=true
end
This will use the User class (Admin would have been created):
factory :admin '''class: User''' do
sequence(:name) { |n| "NewName #{n}" }
fullname {"test_user"}
email {"sjolly@ncsu.edu"}
parent_id =1
is_new_user=true
end

It's possible to set up associations within factories. If the factory name is the same as the association name, the factory name can be left out, as given below :

Factory for Assignment having associations with instructor and wiki_type:

factory :assignment_without_name, class: Assignment do
name {}
submitter_count {3}
is_coding_assignment {true}
microtask {true}
review_assignment_strategy {'Auto-Selected'}
'''''association :instructor, factory: :user'''''
'''association :wiki_type, factory: :wiki_typ'''e''
end

===Creating specs ===

*Create a assignment_spec.rb file in spec/models folder

An example of a test case is
<code>require 'spec_helper'

describe "Team_Assignment" do
it "checks team assignment should be true" do
assign=FactoryGirl.create(:assignment)
res=assign.team_assignment
expect(res).to be true
end</code>

==Tested Spec Methods==

'''team_Assignment''': The methods returns true by default indicating it is a team assignment. The rspec method '''#team_assignment''' checks whether the method returns true or not

'''has_Teams''': The method in the assignment model returns true or false depending upon whether the assignement has one or more teams associated with it. The corresponding rspec method '''#has_teams?''' checks whether the method returns true when a team has been assigned to it.

'''has_Topics''': The method in the assignment model returns true or false depending upon whether the assignment has one or more topics associated with it. The corresponding rspec method '''#has_topics'''? checks whether the method returns true when a team has been assigned to it.

'''is_wiki_assignment''': The method in the assignment model returns true or false depending upon whether the assignment is a wiki assignment or not. It returns true if its '''wiki_type_id > 1'''. The corresponding rspec method '''#is_wiki_assignment''' validates that the model method returns true when the assignment is a wiki assignment with wiki_type_id >1

'''is_google_doc''': The method in the assignment model returns true or false depending upon whether the assignment is a google document or not. It returns true if its '''wiki_type_id =4'''. The corresponding rspec method #is_google_doc validates that the model method returns true when the assignment is a google document with wiki_type_id =4

is_microtask: The method in the assignment model returns true or false depending upon whether the assignment is a microtask or not. It returns true if the microtask variable isassigned true in the assignment. The corresponding rspec method '''#is_microtask?''' validates that the model method returns true when the microtask variable is assigned true in the assignment

'''dynamic_reviewer_assignment''': The method in the assignment model checks whether the '''review_assignment_strategy''' is set to ''''Auto-Selected'''' or not. It returns true if the review_assignment_strategy value is set to ‘Auto-Selected’. The corresponding rspec method '''#dynamic_reviewer_assignment?''' validates that the model method returns true when the review_assignment_strategy is set to 'Auto-Selected'.

'''candidate_assignment_teams_to_review''': The spec method '''#candidate_assignment_teams_to_review''' validates whether the model method returns nil when there are no contributors to the assignment in the team

'''candidate_topics_for_quiz''': The corresponding spec method validates whether the model method returns nil if the assignment has no sign up topic

===Running RSpec===

$ rspec spec/models/assignment_spec.rb
You should be able to run tests successfully and see the following message:
Finished in 1.11 seconds (files took 14.47 seconds to load)
14 examples, 0 failures

==References==
<References/>