Expertiza_Wiki - User contributions [en]

Text metrics

2016-11-10T04:36:30Z

Dsiva: /* Proposed Design */

This is the design review of our final project as part of CSC 517 in Fall 2016.
The Project is titled Text Metrics.

===Description===

This project will facilitate few text metrics to evaluate student's peer reviews.
The text metrics will provide a result about the textual content, the nature of the review, whether it contains any sort of offensive or improper language, and quantify the sincerity of the review in general.

===Tasks to be completed===

#Create DB table [review_metrics] to record all the metrics of volume, presence of suggestions, errors/problems pointed out by the reviewer and offensive words used in the review text if any.
#Add a pop-up dialog or a label for both students (student_review/list) and for instructors by adding content in review_mapping/response_report page metrics column
#Make sure the code works for both assignments with and without "vary rubric by rounds" selected.
#Make sure the code updates the review text metrics table when the peer reviews are updated.
#Sort the reviews based on the text metrics on the “Your scores” pages of students’ view
#Create tests to make sure the test coverage increases

===Current Implementation===
Currently, after completion of reviews, the reviewers can view their responses as shown in the screenshot below:

Instructors can see the response of the reviewers. However, in order to analyze the quality of review given by the students, the instructors have to manually go through all the reviews given by every student one at a time. This could be a time-consuming process, and the reviewers may not be properly assessed.

In order to ease the process of evaluating the reviewers, metrics that can analyze the text written by the reviewers can be added. This will give more information about the reviews given by the reviewers to the instructors evaluating them.

[[File:Capture1981.PNG]]

===Proposed Design===

With reference to the current tasks, we will be adding a new model
Review_metrics. This model will include all the metrics as follows:

#response_id → int(11) → foreign key
#volume → int(11) → # of [different] words
#suggestion → tinyint(1) → if suggestion is given in the peer-review
#problem → tinyint(1) → if problems or errors in the artifact are pointed out in the peer-review
#offensive_term → tinyint(1) → if the peer-review contains any offensive terms

There will be a consequent review_metric_controller which will include all the necessary CRUD operations
for review metrics such as add, remove and update review metrics.

We will be dealing with the following View files:

# student_review/list.html.erb - for the student
# review_mapping/response_report.html.erb - for the instructor

==== Design Pattern Used ====
Iterator pattern is used as the design pattern. This pattern is used in order to allow us to iterate over the elements of a collection regardless of their implementation. In our case, the collection is the different responses given by a reviewer in one single feedback. Since we will be iterating over the different responses in a given feedback by a reviewer (where the different responses in a given feedback are the elements of the collection) in order to collect the text metrics, the design pattern used will be an iterator pattern. This will provide a standard interface for starting an iteration and moving to the next element, regardless of the implementation of the collection.

====Features to be added====

Added label or pop up which will indicate the metrics as icons, as shown below.
These icons will directly summarize the review in terms of predefined metrics. The reviews will be sorted according to the text metrics and will be displayed to the student on the 'Your Scores' page.

Text metrics

2016-11-10T04:36:11Z

Dsiva: /* Proposed Design */

Text metrics

2016-11-10T00:40:11Z

Dsiva: Created page with "This is the design review of our final project as part of CSC 517 in Fall 2016. The Project is titled Text Metrics. ===Description=== This project will facilitate few text met..."

This is the design review of our final project as part of CSC 517 in Fall 2016.
The Project is titled Text Metrics.

===Description===

This project will facilitate few text metrics to evaluate student's peer reviews.
The text metrics will provide a result about the textual content, the nature of the review, whether it contains any sort of offensive or improper language, and quantify the sincerity of the review in general.

===Tasks to be completed===

#Create DB table [review_metrics] to record all the metrics of volume, presence of suggestions, errors/problems pointed out by the reviewer and offensive words used in the review text if any.
#Add a pop-up dialog or a label for both students (student_review/list) and for instructors by adding content in review_mapping/response_report page metrics column
#Make sure the code works for both assignments with and without "vary rubric by rounds" selected.
#Make sure the code updates the review text metrics table when the peer reviews are updated.
#Sort the reviews based on the text metrics on the “Your scores” pages of students’ view
#Create tests to make sure the test coverage increases

===Current Implementation===
Currently, after completion of reviews, the reviewers can view their responses as shown in the screenshot below:

Instructors can see the response of the reviewers. However, in order to analyze the quality of review given by the students, the instructors have to manually go through all the reviews given by every student one at a time. This could be a time-consuming process, and the reviewers may not be properly assessed.

In order to ease the process of evaluating the reviewers, metrics that can analyze the text written by the reviewers can be added. This will give more information about the reviews given by the reviewers to the instructors evaluating them.

===Proposed Design===

With reference to the current tasks, we will be adding a new model
Review_metrics. This model will include all the metrics as follows:

#response_id → int(11) → foreign key
#volume → int(11) → # of [different] words
#suggestion → tinyint(1) → if suggestion is given in the peer-review
#problem → tinyint(1) → if problems or errors in the artifact are pointed out in the peer-review
#offensive_term → tinyint(1) → if the peer-review contains any offensive terms

There will be a consequent review_metric_controller which will include all the necessary CRUD operations
for review metrics such as add, remove and update review metrics.

We will be dealing with the following View files:

# student_review/list.html.erb - for the student
# review_mapping/response_report.html.erb - for the instructor
Since we will be iterating over the different responses in a given feedback by a reviewer (where the different responses in a given feedback are the elements of the collection) in order to collect the text metrics, the design pattern used will be an iterator pattern.

====Features to be added====

Added label or pop up which will indicate the metrics as icons, as shown below.
These icons will directly summarize the review in terms of predefined metrics. The reviews will be sorted according to the text metrics and will be displayed to the student on the 'Your Scores' page.

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T22:28:15Z

Dsiva: /* Running Tests From Terminal */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps in UI==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

In order to test using the UI, type the following commands to start the server:

''git clone https://github.com/517OSS/expertiza.git
bundle install
rake db:migrate
rails s
''
Once the Expertiza website is up, test the following:

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Running Tests From Terminal ==
The test file we added is 'staggered_deadline_spec.rb'. Once the server is running, open a new terminal, navigate the cloned 'expertiza' folder. The tests can be run in the terminal using the command:

''rspec /spec/features/staggered_deadline_spec.rb
''

Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T22:27:32Z

Dsiva: /* Running Tests From Terminal */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps in UI==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

In order to test using the UI, type the following commands to start the server:

''git clone https://github.com/517OSS/expertiza.git
bundle install
rake db:migrate
rails s
''
Once the Expertiza website is up, test the following:

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Running Tests From Terminal ==
The test file we added is 'staggered_deadline_spec.rb'. Once the server is running, open a new terminal, navigate the cloned 'expertiza' folder. The tests can be run in the terminal using the command:

''rspec /spec/features/staggered_deadline_spec.rb''.

Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T22:26:55Z

Dsiva: /* Running Tests From Terminal */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps in UI==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

In order to test using the UI, type the following commands to start the server:

''git clone https://github.com/517OSS/expertiza.git
bundle install
rake db:migrate
rails s
''
Once the Expertiza website is up, test the following:

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Running Tests From Terminal ==
The test file we added is 'staggered_deadline_spec.rb'. Once the server is running, open a new terminal, navigate the cloned 'expertiza' folder. The tests can be run in the terminal using the command: ''rspec /spec/features/staggered_deadline_spec.rb''.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T22:24:05Z

Dsiva: /* Test Steps in UI */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps in UI==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

In order to test using the UI, type the following commands to start the server:

''git clone https://github.com/517OSS/expertiza.git
bundle install
rake db:migrate
rails s
''
Once the Expertiza website is up, test the following:

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Running Tests From Terminal ==
The test file we added is 'staggered_deadline_spec.rb'. The tests can be run in the terminal using the command: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T22:23:03Z

Dsiva: /* Test Steps in UI */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps in UI==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

In order to test using the UI, type the following commands:

''git clone https://github.com/517OSS/expertiza.git
bundle install
rake db:migrate
rails s
''
Once the Expertiza website is up, test the following:

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Running Tests From Terminal ==
The test file we added is 'staggered_deadline_spec.rb'. The tests can be run in the terminal using the command: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T22:21:47Z

Dsiva: /* Test Steps in UI */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps in UI==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

#In order to test using the UI, clone our GitHub repository

# git clone https://github.com/517OSS/expertiza.git
# bundle install
# rake db:migrate
# rails s

# Once the Expertiza website is up, test the following:

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Running Tests From Terminal ==
The test file we added is 'staggered_deadline_spec.rb'. The tests can be run in the terminal using the command: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T04:01:28Z

Dsiva: /* Test from UI */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps in UI==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Running Tests From Terminal ==
The test file we added is 'staggered_deadline_spec.rb'. The tests can be run in the terminal using the command: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T04:01:00Z

Dsiva: /* Test Steps */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps in UI==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Test from UI ==
The test file we added is 'staggered_deadline_spec.rb'. The tests can be run in the terminal using the command: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T03:56:23Z

Dsiva: /* Project Description and Test Strategy */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of different topics under the same assignment may need to be different for reasons like dependency of one topic on another. The aim of this project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1.

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Test from UI ==
The test file we added is 'staggered_deadline_spec.rb'. The tests can be run in the terminal using the command: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T03:52:22Z

Dsiva: /* Project Description and Test Strategy */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline means having different deadlines for different topics under the same assignment. This is a relatively new feature of Expertiza. Deadline of topics can be changed due to specific reasons (like dependencies), without affecting the deadline of other topics. This project is to write RSpec tests to test the functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' Two students with different topics submit their work before the assignment's submission deadline in round 1

'''Scenario 1:''' Change deadline of topic 1 to bring it into review stage in round 1, check if the student assigned with topic 1 can review others' work, check if the rubrics are right for round 1.

'''Scenario 2:''' Change the deadlines of both the topics to bring them into review stage in round 2, check if the students assigned with these topics can review each other's work, check if the rubrics are right for round 2.

'''Scenario 3:''' Change the deadline of both the topic to bring them into finish stage in round 2, check that the students assigned with these topics are unable to review each other.

== Test Steps ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Test from UI ==
The test file we added is 'staggered_deadline_spec.rb'. The tests can be run in the terminal using the command: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-11-04T03:25:11Z

Dsiva:

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[https://en.wikipedia.org/wiki/Functional_testing Functional testing] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description and Test Strategy==
Staggered deadline is deadline for individual topic under the same assignment. This is a relatively new feature of Expertiza. Deadline of topics could be changed due to specific reasons without affect other topics. This project is to write RSpec tests to test functionality of staggered deadline using Capybara. According to the instruction, we design 3 test cases:

'''Initial state:''' two students with different topics submit their works before the assignment's submission deadline in round 1

'''Case 1:''' change topic 1's deadline to bring it into review stage in round 1, check if he could review others work, check if the rubrics is correct for the round 1

'''Case 2:''' change both topics' deadlines to bring them into review stage in round 2, check if they could review each other, check if the rubrics is correct for the round 2

'''Case 3:''' change both topic's deadlines to bring them into finish stage in round 2, check if they could not review each other

== Test Steps ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Test from UI ==
The test file we added is 'staggered_deadline_spec.rb'. The tests can be run in the terminal using the command: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result:

[[File:Result.jpg‎ ]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-10-29T03:02:23Z

Dsiva:

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info/documentation/ Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[[Capybara (software)|Capybara]] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[[Functional testing]] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description ==
This project is to write RSpec tests to test functionality of Staggered deadline in Expertiza using Capybara. The procedures to be tested are:
* Create an assignment.
* Submit a topic.
* Change a topic deadline.
* View topic stage.
* Submit reviews.

== Test Plan ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.
== Execution ==
The command used to execute the RSpec test was 'rspec /spec/features/staggered_deadline_spec.rb'.
[[File:Execution.jpg]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

File:12874325 1141331805910848 864500454 o.jpg

2016-10-29T03:00:22Z

Dsiva:

File:Execution.jpg

2016-10-29T02:56:48Z

Dsiva: uploaded a new version of "File:Execution.jpg"

File:Execution.jpg

2016-10-29T02:55:43Z

Dsiva:

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-10-29T02:55:16Z

Dsiva: /* Execution */

{{R from move}}

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info/documentation/ Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[[Capybara (software)|Capybara]] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[[Functional testing]] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description ==
This project is to write RSpec tests to test functionality of Staggered deadline in Expertiza using Capybara. The procedures to be tested are:
* Create an assignment.
* Submit a topic.
* Change a topic deadline.
* View topic stage.
* Submit reviews.

== Test Plan ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.
== Execution ==
The command used to execute the RSpec test was 'rspec /spec/features/staggered_deadline_spec.rb'.
[[File:Execution.jpg]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-10-29T02:49:46Z

Dsiva:

{{R from move}}

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignments and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment.The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info/documentation/ Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[[Capybara (software)|Capybara]] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[[Functional testing]] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description ==
This project is to write RSpec tests to test functionality of Staggered deadline in Expertiza using Capybara. The procedures to be tested are:
* Create an assignment.
* Submit a topic.
* Change a topic deadline.
* View topic stage.
* Submit reviews.

== Test Plan ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.
== Execution ==
The command used to execute the RSpec test was 'rspec /spec/features/staggered_deadline_spec.rb'.
[[File:Execution.jpg.jpg|center|thumb|981x981px]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

File:Execution of expertiza.png

2016-10-29T02:09:54Z

Dsiva:

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-10-29T02:09:25Z

Dsiva: /* Execution */

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignmnets and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment. The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info/documentation/ Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[[Capybara (software)|Capybara]] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[[Functional testing]] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description ==
This project is to write RSpec tests to test functionality of Staggered deadline in Expertiza using Capybara. The procedures to be tested are:
* Create an assignment.
* Submit a topic.
* Change a topic deadline.
* View topic stage.
* Submit reviews.

== Test Plan ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Execution ==
[[File:execution_of_expertiza.png]]

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

File:Execution of expertiza.PNG

2016-10-29T02:08:33Z

Dsiva: Execution of Summary

Execution of Summary

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-10-29T02:01:53Z

Dsiva:

== Introduction ==
[https://github.com/expertiza/expertiza Expertiza] is a web application which enables students to choose a topic in an assignment, submit assignmnets and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment. The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
[http://rspec.info/documentation/ Rspec] is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core
# rspec-expectations
# rspec-mocks
# rspec-rails

=== Capybara ===
[[Capybara (software)|Capybara]] is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
[[Functional testing]] is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description ==
This project is to write RSpec tests to test functionality of Staggered deadline in Expertiza using Capybara. The procedures to be tested are:
* Create an assignment.
* Submit a topic.
* Change a topic deadline.
* View topic stage.
* Submit reviews.

== Test Plan ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Execution ==

== References ==
# [https://github.com/expertiza/expertiza Expertiza]
# [http://rspec.info/documentation/ RSpec Documentation]
# [https://en.wikipedia.org/wiki/Capybara_(software) Capybara]
# [https://en.wikipedia.org/wiki/Functional_testing Functional Testing]

CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality

2016-10-29T00:50:54Z

Dsiva: Staggered Deadline

== Introduction ==
Expertiza is a web application which enables students to choose a topic in an assignment, submit assignmnets and peer review others' work. This application also allows the instructors to add assignments to a course, and create multiple topics with varying rubrics and different deadlines for an assignment. The Expertiza project is developed on Open Source Software (OSS) and is supported by the National Science Foundation.

== Background ==

=== Rspec ===
Rspec is a behavior-driven development tool for Ruby programmers which helps write human readable specifications that direct and validate the development of an application. RSpec is composed of multiple libraries which can be used together or independently with other testing tools like Capybara and Cucumber. There are four parts of RSpec. They are:
# rspec-core:
# rspec-expectations:
# rspec-mocks:
# rspec-rails:

=== Capybara ===
Capybara is a web-based test automation software that simulates scenarios for user stories. It can automate web application testing for behavior-driven software development (BDD). It is a gem that can be used on top of a web-based driver. It offers a user-friendly domain specific language to describe a sequence of actions executed by the web driver. It is a part of the Cucumber testing framework.

It is supported by the following web-based drivers:
* RackTest
* Selenium
* Capybara-webkit

=== Functional Testing ===
Functional testing is a type of black-box testing used in quality assurance, Functional tests are done by feeding the inputs and checking the outputs giving least importance to the internal structure of the program. It describes what the system does. Functional testing verifies a program by checking it against the specification documents. There are different types of functional testing:
* Smoke testing
* Sanity testing
* Regression testing
* Usability testing

== Project Description ==
This project is to write RSpec tests to test functionality of Staggered deadline in Expertiza using Capybara. The procedures to be tested are:
* Create an assignment.
* Submit a topic.
* Change a topic deadline.
* View topic stage.
* Submit reviews.

== Test Plan ==
Our test plan is divided into the following steps:
# Create an assignment: Create an assignment with topic with varying rubric by round feature.
# Add participants to newly created assignment.
# Submit a Topic: Impersonate each participant, choose a topic and submit something.
# Change topic Deadline: Change deadline of each topic and let each topic be in different stages (like submission round 1, review round 1, submission round 2 and review round 2)
# View topic stage: Impersonate each participant and check their topic’s current stage on student_task#list view.
# Submit reviews: Participant with topic in review stage can review other participant’s work, ensuring that right rubrics are used for different topics.The reviewers can fill in the rubrics, save and submit their reviews successfully.

==== Create an Assignment: ====
# Login as instructor 'instructor6'
# Click on 'Create public assignment'.
# Fill in the textboxes with assignment name, and assignment directory and other necessary details.
# Click the 'Create' button.
# Click on the link 'Rubrics'.
# Check the box 'Review rubric varies by round?'.
# Click on 'Save'.
# Click the link 'Topics'.
# Click on 'New topic'
# Fill in the Topic id, Topic name,Topic category and Number of slots.
# Click 'Create'.
After returning, the assignment created is listed under 'Assignments' tab.

==== Add Participants to Newly Created Assignment: ====
# Create a new assignment 'Assignment1665' using factories, with two review rounds and Staggered Deadline enabled.
# Added three participants to the newly created assignment using factories.

==== Submit a topic: ====
# Create a stub to Impersonate the student 'student2064'.
# Click on 'Assignment1665' from the task list.
# Click on ‘Your Work’.
# Fill in the textbox with the submission link.
# Click on ‘upload link’
On clicking the 'upload' button, the submitted link is displayed on the page.

==== Change Topic Deadline: ====
# Create an assignment 'Assignment1665' using factories, with two rounds of reviews, and the staggered deadline functionality enabled.
# Create different types of deadlines with names 'submission', 'review', 'metareview', 'drop_topic', 'signup' and 'team_formation'.
# Create two topics 'Topic_1' and 'Topic_2' under 'Assignment1665' using factories.
# Create assignment due dates for 'submission' and 'review' for two rounds using factories.
# Set the topic due dates to corresponding assignment due dates using factories.
# Change the different deadlines of one topic to different dates.
On returning, click on 'Assignments' tab, and click on 'Edit' under 'Actions'. Click on the 'Topics' tab and then click the link 'Show start/due dates'. The instructor should be able to see the changed due dates for each of the topics

==== View Topic Stages: ====
# Change the deadline date of topic assigned to 'student2064' to a past date and change deadline date of topic assigned to 'student2065' to a future date.
# Impersonate a participant 'student2064' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Review'
# Impersonate 'student2065' using a stub.
# Click on 'Assignments' tab on top of the page.
# The page should display the current stage of 'Assignment1665' as 'Submission'

==== Submit Review: ====
# Impersonate 'student2064' using a stub.
# Click on the link 'Assignment1665'.
# Click on the link 'Others' work'.
# Select a topic to be reviewed.
# Click on the link 'Begin'.
# The student can see 'Questionnare1' for the review round 1.
# Fill in the response checkboxes.
# Click the button 'Save Review'.
On returning, the reviewer should be able to see the 'View' option for the reviews done.

== Execution ==