Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:59:44Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
[https://travis-ci.org Travis CI] is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with [http://rspec.info/ RSpec]:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==
1. First, using [https://github.com/expertiza/expertiza/blob/master/spec/factories/factories.rb factories] to create test data: create assignment, create topic, create participant.
''before(:each) do
create(:assignment, name: "Assignment1684", directory_path: "Assignment1684")
create_list(:participant, 3)
create(:topic, topic_name: "Topic")
create(:deadline_type, name: "submission")
create(:deadline_type, name: "review")
create(:deadline_type, name: "metareview")
create(:deadline_type, name: "drop_topic")
create(:deadline_type, name: "signup")
create(:deadline_type, name: "team_formation")
create(:deadline_right)
create(:deadline_right, name: 'Late')
create(:deadline_right, name: 'OK')
create(:assignment_due_date, deadline_type: DeadlineType.where(name: "submission").first, due_at: DateTime.now + 1)
end''
2. Mock the workflow of Assignment submission using Capybara.

[[File:Work flow.png]]

3. Check the result of the submission both from webpage and database.

In database level, the submission results are stored in table: TEAMS.

[[File:Teams.jpg]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:57:33Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
[https://travis-ci.org Travis CI] is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with [http://rspec.info/ RSpec]:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==
1. First, using [https://github.com/expertiza/expertiza/blob/master/spec/factories/factories.rb factories] to create test data: create assignment, create topic, create participant.
''before(:each) do
create(:assignment, name: "Assignment1684", directory_path: "Assignment1684")
create_list(:participant, 3)
create(:topic, topic_name: "Topic")
create(:deadline_type, name: "submission")
create(:deadline_type, name: "review")
create(:deadline_type, name: "metareview")
create(:deadline_type, name: "drop_topic")
create(:deadline_type, name: "signup")
create(:deadline_type, name: "team_formation")
create(:deadline_right)
create(:deadline_right, name: 'Late')
create(:deadline_right, name: 'OK')
create(:assignment_due_date, deadline_type: DeadlineType.where(name: "submission").first, due_at: DateTime.now + 1)
end''
2. Mock the workflow of Assignment submission using Capybara.

3. Check the result of the submission both from webpage and database.

In database level, the submission results are stored in table: TEAMS.

[[File:Teams.jpg]]

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:57:16Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
[https://travis-ci.org Travis CI] is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with [http://rspec.info/ RSpec]:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==
1. First, using [https://github.com/expertiza/expertiza/blob/master/spec/factories/factories.rb factories] to create test data: create assignment, create topic, create participant.
''before(:each) do
#create assignment and topic
create(:assignment, name: "Assignment1684", directory_path: "Assignment1684")
create_list(:participant, 3)
create(:topic, topic_name: "Topic")
create(:deadline_type, name: "submission")
create(:deadline_type, name: "review")
create(:deadline_type, name: "metareview")
create(:deadline_type, name: "drop_topic")
create(:deadline_type, name: "signup")
create(:deadline_type, name: "team_formation")
create(:deadline_right)
create(:deadline_right, name: 'Late')
create(:deadline_right, name: 'OK')
create(:assignment_due_date, deadline_type: DeadlineType.where(name: "submission").first, due_at: DateTime.now + 1)
end''
2. Mock the workflow of Assignment submission using Capybara.

3. Check the result of the submission both from webpage and database.

In database level, the submission results are stored in table: TEAMS.

[[File:Teams.jpg]]

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:56:58Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
[https://travis-ci.org Travis CI] is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with [http://rspec.info/ RSpec]:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==
1. First, using [https://github.com/expertiza/expertiza/blob/master/spec/factories/factories.rb factories] to create test data: create assignment, create topic, create participant.
''before(:each) do
#create assignment and topic
create(:assignment, name: "Assignment1684", directory_path: "Assignment1684")
create_list(:participant, 3)
create(:topic, topic_name: "Topic")
create(:deadline_type, name: "submission")
create(:deadline_type, name: "review")
create(:deadline_type, name: "metareview")
create(:deadline_type, name: "drop_topic")
create(:deadline_type, name: "signup")
create(:deadline_type, name: "team_formation")
create(:deadline_right)
create(:deadline_right, name: 'Late')
create(:deadline_right, name: 'OK')
create(:assignment_due_date, deadline_type: DeadlineType.where(name: "submission").first, due_at: DateTime.now + 1)
end''
2. Mock the workflow of Assignment submission using Capybara.
3. Check the result of the submission both from webpage and database.

In database level, the submission results are stored in table: TEAMS.

[[File:Teams.jpg]]

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

File:Teams.jpg

2016-11-13T23:52:08Z

Lshi7:

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:51:37Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
[https://travis-ci.org Travis CI] is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with [http://rspec.info/ RSpec]:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==
# First, using [https://github.com/expertiza/expertiza/blob/master/spec/factories/factories.rb factories] to create test data: create assignment, create topic, create participant.
# Mock the workflow of Assignment submission using Capybara.
# Check the result of the submission both from webpage and database.

In database level, the submission results are stored in table: TEAMS.

[[File:Teams.jpg]]

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:50:49Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
[https://travis-ci.org Travis CI] is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with [http://rspec.info/ RSpec]:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==
# First, using [https://github.com/expertiza/expertiza/blob/master/spec/factories/factories.rb factories] to create test data: create assignment, create topic, create participant.
# Mock the workflow of Assignment submission using Capybara.
# Check the result of the submission both from webpage and database.
In database level, the submission results are stored in table: TEAMS.

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:40:30Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
[https://travis-ci.org Travis CI] is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with [http://rspec.info/ RSpec]:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==

Mock the workflow of Assignment submission using Capybara and check the result of the submission.

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:35:10Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
[https://travis-ci.org Travis CI] is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
[https://github.com/jnicklas/capybara Capybara] supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with [http://rspec.info/ RSpec]:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==

Mock the flow of Assignment submission using Capybara and check the result of the submission.

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:33:13Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios:

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

== '''Background''' ==

=== Travis CI ===
Travis CI is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
Capybara supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with RSpec:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==

Mock the flow of Assignment submission using Capybara and check the result of the submission.

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:28:22Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios.

== '''Background''' ==

=== Travis CI ===
Travis CI is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
Capybara supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with RSpec:'''
Load RSpec 2.x support by adding the following line(typically to the spec_helper.rb file):
''require 'capybara/rspec'
''

== '''Approach''' ==

Mock the flow of Assignment submission using Capybara and check the result of the submission.

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

=== Scenarios ===

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:22:06Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios.

== '''Background''' ==

=== Travis CI ===
Travis CI is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
Capybara supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

'''Using Capybara with RSpec:'''
Load RSpec 2.x support by adding the following line:
''require 'capybara/rspec'
''

== '''Approach''' ==

Mock the flow of Assignment submission using Capybara and check the result of the submission.

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

=== Scenarios ===

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-13T23:21:02Z

Lshi7:

== '''Introduction to Expertiza''' ==
[https://github.com/expertiza/expertiza Expertiza] is an open-source project on GitHub used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios.

== '''Background''' ==

=== Travis CI ===
Travis CI is a hosted, distributed continuous integration service used to build and test software projects hosted at GitHub.

'''Configuration:'''
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.

'''Operation:'''
When Travis CI has been activated for a given repository, GitHub will notify it whenever new commits are pushed to that repository or a pull request is submitted. It can also be configured to only run for specific branches, or branches whose names match a specific pattern. Travis CI will then check out the relevant branch and run the commands specified in .travis.yml, which usually build the software and run any automated tests. When that process has completed, Travis notifies the developer(s) in the way it has been configured to do so—for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. In the case of pull requests, the pull request will be annotated with the outcome and a link to the build log, using a GitHub integration.

=== Capybara ===
Capybara supports selenium-webdriver, which is mostly used in web-based automation frameworks. It supports JavaScript, can access HTTP resources outside of application, and can also be setup for testing in headless mode which is especially useful for CI scenarios.

Using Capybara with RSpec:
Load RSpec 2.x support by adding the following line:
''require 'capybara/rspec'
''

== '''Approach''' ==

Mock the flow of Assignment submission using Capybara and check the result of the submission.

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

=== Scenarios ===

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-10T02:43:14Z

Lshi7:

== '''Introduction to Expertiza''' ==
Expertiza is an online system that is used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

Expertiza is an open-source project with the source code available as a public repository on GitHub. It is developed using Ruby on Rails and is increasingly becoming robust thanks to the innumerable bugs being fixed by the community. The project has a micro-blog on SourceForge where the developer community report bugs and document updates.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios.

== '''Approach''' ==

Mock the flow of Assignment submission using Capybara and check the result of the submission.

===Workflow===
Insert test database: create assignment, create topic, create participant.

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

=== Scenarios ===

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

CSC/ECE 517 Fall 2016

2016-11-10T02:41:07Z

Lshi7:

[http://www.example.com link title]==Calibration Assignment Submissions==
*[[Calibration Assignment Submission (Firebrick JS)]]
*[[Calibration Assignment Submission (Active Job)]]
==Writing Assignments 2==
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]
*[[CSC/ECE 517 Fall 2016/E1643. Refactor Suggestion controller]]
*[[CSC/ECE 517 Fall 2016/E1631. Refactoring Bidding Interface]]
*[[CSC/ECE 517 Fall 2016/E1674.Refactor leaderboard.rb and write unit tests]]
*[[CSC/ECE 517 Fall 2016/E1671. Unit Tests for participants.rb Hierarchy]]
*[[CSC/ECE 517 Fall 2016/E1668.Test e-mailing functionality]]
*[[CSC/ECE 517 Fall 2016/E1658. Refractor lottery_controller.rb and write integration tests]]
*[[CSC/ECE 517 Fall 2016/E1660. Review requirements and thresholds]]
*[[CSC/ECE 517 Fall 2016/E1650. Sort instructor views alphabetically by default]]
*[[CSC/ECE 517 Fall 2016/E1644. Refactor and test Teams Controller]]
*[[CSC/ECE 517 Fall 2016/E1645. Refactoring Tree Display Controller]]
*[[CSC/ECE 517 Fall 2016/E1659. Refactor on_the_fly_calc.rb]]
*[[CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors]]
*[[CSC/ECE 517 Fall 2016/E1653. Fix and improve rubric criteria]]
*[[CSC/ECE 517 Fall 2016/E1642. Refactor review_response_map.rb]]
*[[CSC/ECE 517 Fall 2016/E1633. Refactor different question types from quiz feature]]
*[[CSC/ECE_517_Fall_2016/E1664:_Feature_Test_Assignment_Creation]]
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]
*[[CSC/ECE_517_Fall_2016/E1654. Improve_date-picker_and_deadlines]]
*[[CSC/ECE_517_Fall_2016/E1652 Fix teammate advertisements and requests to join a team ]]
*[[CSC/ECE_517_Fall_2016/E1662. UI issues/fixes]]
*[[CSC/ECE_517_Fall_2016/E1673. Refactor question_type.rb]]
*[[CSC/ECE_517_Fall_2016/E1675. Timestamp for student file & hyperlink submissions]]
*[[CSC/ECE_517_Fall_2016/E1640. Refactor response.rb and response_helper.rb]]
*[[CSC/ECE 517 Fall 2016/E1634. Refactor and write unit test of due_date.rb and deadline_helper.rb]]
*[[CSC/ECE_517_Fall_2016/M1654._Improve_network_security_features]]
*[[CSC/ECE_517_Fall_2016/E1670._Unit_tests_for_answers.rb]]
*[[CSC/ECE_517_Fall_2016/E1641. Refactor review_mapping_controller.rb]]
*[[CSC/ECE_517_Fall_2016/M1652_Implement_ImageMap_Support_Servo]]
*[[CSC/ECE_517_Fall_2016/E1648/Add_past_due_assignment]]
*[[CSC/ECE 517 Fall 2016/E1656. Improve imports]]
*[[CSC/ECE_517_Fall_2016/M1653_Implement_HTML_form_validation]]
*[[CSC/ECE_517_Fall_2016/E1635._Refactor_join_team_requests_controller.rb_and_invitation_controller.rb]]
*[[CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality]]

==Final Project Design Document==
*[[CSC/ECE 517 Fall 2016 E1696 Improve Self-Review]]
*[[CSC/ECE 517 Fall 2016 E1676 Role-based reviewing]]
*[[CSC/ECE 517 Fall 2016/E1680. Improve survey functionality]]
*[[CSC/ECE 517 Fall 2016/E1693. Drag-and-drop interface for creating rubrics]]
*[[CSC/ECE 517 Fall 2016/E1701. Accelerate RSpec testing]]
*[[CSC/ECE 517 Fall 2016/E1705. Tracking the time students look at the others' submissions]]
*[[CSC/ECE 517 Fall 2016/E1688. Send feedback to support + tree display improvement]]
*[[CSC/ECE 517 Fall 2016 E1707: Top trading cycles to exclude previous teammates]]
*[[CSC/ECE 517 Fall 2016 E1678: Review configuration options]]
*[[CSC/ECE 517 Fall 2016 E1682: Improve score calculation]]
*[[CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission]]
*[[CSC/ECE 517 Fall 2016 E1689: Anonymous Chat Between Author and Reviewer]]
*[[CSC/ECE 517 Fall 2016 E1703: Logging for Expertiza]]
*[[CSC/ECE 517 Fall 2016 E1708: Improvements to staggered-deadline assignments]]
*[[CSC/ECE 517 Fall 2016 E1685: UI changes for review and score reports]]
*[[CSC/ECE 517 Fall 2016/ M1653 Implement HTML form validation]]
*[[CSC/ECE 517 Fall 2016/ E1700 Integrate Google doc editor/viewer]]
*[[CSC/ECE_517_Fall_2016/M1652_ImageMap_Support_Servo]]

CSC/ECE 517 Fall 2016 E1684: Feature Test for Assignment Submission

2016-11-10T02:31:06Z

Lshi7:

== '''Introduction to Expertiza''' ==
Expertiza is an online system that is used by students to view/submit assignments and review others' work. Expertiza also provides tools to visualize the scores and gauge the improvements made during the course semester. It also facilitates and monitors team projects. It is targeted at educational and non-profit organizations.

Expertiza is an open-source project with the source code available as a public repository on GitHub. It is developed using Ruby on Rails and is increasingly becoming robust thanks to the innumerable bugs being fixed by the community. The project has a micro-blog on SourceForge where the developer community report bugs and document updates.

== '''Project Requirement''' ==

There should be a feature test for submission of the assignment by the student. Once the assignment is created by the instructor the only call to action for the student is assignment submission. The purpose of this project is to test whether the submission function could work properly under different scenarios.

== '''Approach''' ==

Mock the flow of Assignment submission using Capybara and check the result of the submission.

===Workflow===

Student login -> click on the assignment -> upload link or upload file

[[File:Work flow.png]]

=== Scenarios ===

# Upload valid link
# Upload invalid link
# Upload multiple links
# Upload empty link
# Upload file

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

2016-11-02T00:05:07Z

Lshi7: /* Project Description */

== 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 ==
It is a test file. You can test it by running command in terminal: '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-02T00:04:52Z

Lshi7: /* Test Plan */

== 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 ==
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 ==
It is a test file. You can test it by running command in terminal: '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-02T00:03:56Z

Lshi7: /* 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 ==
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 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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: '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]

File:Result.jpg

2016-11-02T00:03:12Z

Lshi7:

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

2016-11-02T00:02:15Z

Lshi7: /* Project Description */

== 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 ==
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 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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result.
[[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-11-02T00:01:49Z

Lshi7: /* Project Description */

== 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 ==
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 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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result.
[[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-11-02T00:01:38Z

Lshi7: /* Project Description */

== 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 ==
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 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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result.
[[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-11-02T00:00:41Z

Lshi7: /* Project Description */

== 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 ==
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 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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result.
[[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-11-01T23:46:01Z

Lshi7: /* Functional Testing */

== 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 ==
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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result.
[[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-11-01T23:45:08Z

Lshi7: /* Capybara */

== 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 ===
[[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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result.
[[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-11-01T23:43:05Z

Lshi7: /* Rspec */

== 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 ===
[[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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result.
[[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-11-01T23:41:33Z

Lshi7: /* Execution */

== 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.
== Test from UI ==
It is a test file. You can test it by running command in terminal: 'rspec /spec/features/staggered_deadline_spec.rb'.
Here is the result.
[[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]

Testing Staggered Deadline

2016-11-01T16:39:42Z

Lshi7: moved Testing Staggered Deadline to CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality: Add detail to the page name

#REDIRECT [[CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality]]

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

2016-11-01T16:39:42Z

Lshi7: moved Testing Staggered Deadline to CSC/ECE 517 Fall 2016/E1665. Test staggered-deadline functionality: Add detail to the page name

== 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-29T17:39:18Z

Lshi7: /* Execution */

== 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]