Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2016 M1601 Implement HTML5 form validation

2016-04-04T05:09:19Z

Gsrajadh: /* Later Steps */

''' Implementation of HTML5 form validation in servo'''

Servo is a prototype web browser engine being developed by Mozilla and written in the Rust language. This project implements [https://en.wikipedia.org/wiki/HTML5 HTML5] validations for servo. The validations are implemented via methods such as "valueMissing" which determine for different elements such a HTMLInput element etc. if it is ok to leave the input blank or if input is required. The code snippets given in this wiki explain how these methods are called in the HTML elements via different enums. The actual code to validate these inputs, will be implemented in the next phase of the project.

=='''Introduction'''==
The [https://en.wikipedia.org/wiki/HTML5 HTML5]is a markup language used for displaying content on the World Wide Web

HTML5 defines set of specification which users needs to follow to make web pages HTML5 compliant. HTML 5 defines a mechanism by which contents of forms can be validated before user is allowed to submit them. [https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] currently implements support for few of the form elements. This project is intended to implement client-side validations for these elements and extend the existing form element subset to include additional form elements that will support client side validation.

===Servo===
[https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] is an open source prototype web browser layout engine that is being developed by Mozilla Research. It is written in [https://www.rust-lang.org/ Rust] language. Current browser engines are mostly based on single-threaded model. Although there are some tasks (as decompressing images) which can be done on separate processor cores but most of the work (like interpreting HTML and laying out pages) is single-threaded.
Motivation behind servo is to create a highly parallel environment, where different components (such as rendering, layout, HTML parsing, image decoding, etc.) can be handled by fine-grained, isolated tasks.

===Rust===
[http://doc.rust-lang.org/book/README.html Rust] is an open source systems programming language developed by Mozilla Research. Rust is designed to provide the same level of performance and power as C++, but without the risk of bugs and security flaws, and also with built-in mechanisms for exploiting multi-core processors.

=='''Project Description'''==
Write some description here

===Compiling and Building Servo===
* The project requirement initially stated that we build and Compile servo. Following are the steps for this:
Servo is built with [https://mail.mozilla.org/pipermail/rust-dev/2014-March/009090.html Cargo], the Rust package manager. Mozilla's Mach tools are used to orchestrate the build and other tasks.

git clone https://github.com/servo/servo
cd servo
./mach build --dev
./mach run tests/html/about-mozilla.html

===Steps Completed During Last Phase===
* The first requirement was to uncomment the attributes in ValidityState.weidl and fix the resulting build errors by implementing appropriate stub methods in validitystate.rs. This facilitates in declaring the methods which we will be using for validation
* Next, we had to modify the ValidityState constructor to take an &Element argument and store it as element variable of JS<Element> type member in the ValidityState.
* The changes to the constructor resulted in build errors in following files as the constructor was referred to in these files
So, the constructors called in these files were modified to send the required extra parameter.
* Next, we had to add a new enum “ValidityStatus” in ValidityState having each possible validity check in ValidityState. This enum is used to specify the state in order to describe if there is a Value missing or if there is no error and the state is valid
* Next, we had to define a new trait Validatable having method “is_instance_validatable”. (which takes the new ValidityStatus enum as an argument.)
* Next, we implemented this trait and the corresponding method in the following files
* Then, we had to define method as_maybe_validatable in file “element.rs” which returns an &Validatable value if the element implements the newly defined trait. This is used to check if the element is infact validatable before performing further operations to check the form validations
* Finally, we added a new html file “form_html5_validations.html” to test the HTML5 validation for the mentioned conditions

==Requirements==
Our project requirement was to implement client side form validation and extend the supported subset of defined form elements. In order to implement this we were required to implement the following steps:
===Initial Steps===
* We were required to compile Servo and ensure that it runs on tests/html/about-mozilla.html
* Our next requirement was to uncomment the attributes in ValidityState.webidl and implement appropriate stub methods in validitystate.rs in order to fix build errors
*We had to make the ValidityState constructor take an &Element argument and store it as a JS<Element> member in ValidityState
* We had to add a new enum that represents each possible validity check in ValidityState
* We had to define a Validatable trait that contains a method which accepts this enum as an argument
* Implement Validatable trait for the form element types
* We had to use the newly-added JS<Element> member to call the appropriate new methods in ValidityState

===Later Steps===
* We have to add a method to HTMLFormElement to statically validate form element constraints
* Next we need to add a method to HTMLFormElement to interactively validate the constraints of a form element
* We have to implement the checkValidity API and reportValidity API for HTMLFormElement
* We have to Implement each validity state by adding support for attributes such as min,max, minlength etc
* Our last requirement is to modify the form submission algorithm to include constraint validation

==Design==
Blah blah
===Solution Overview===
* Create 3 lists 'control', 'invalid_control', 'unhadled_invalid-control'
* Initialize 'control' with all the submitted elements of the form.
* For each submitted element, check the elements for constraint validation and if check fails - add that element to 'invalid_control' list.
* If the 'invalid_control' list is empty return true.
* For each element in 'invalid_control' list, fire a simple event cancelable at field and if the event was not cancelled - add that element to 'unhadled_invalid-control' list.
* If the 'unhandled_invalid_control' list is empty return true.
* Return false along with the 'unhandled_invalid_control' list to the user_agent, which will focus on one or more of the reported issues to user for further action.

* Implements the validation methods in validitystate.rs
* Each method checks the element submitted to it for a particular constraint like value_missing, range_underflow etc and return false if the constraint check fails.
* Finally, the submit() method of form submission needs to be updated to invoke the interactive_validation() method.

method1: checkValidity
boolean,list<elements> static_validation(list<elements> control){

}

method2: reportValidity
boolean,list<elements> interactive_validation(list<elements> control){
//invoke method 1
status, unhandled_invalid_control = static_validation(control)

if (status==true)
return true, empty_list
else
return false, unhandled_invalid_control
}

===Validation Workflow===
Blah blah

===UML Diagram===
Blah blah

==='''Design Patterns & OO Practices'''===
We were not supposed to modify the existing design apart from adding a new behaviour/ability for HTML Element. We attempted to follow good OO practices throughout development. While using enums and also while defining new methods, we tried to follow the DRY principle in order to avoid repetition of code. Servo has it's own coding standards which are checked by running following command

<code>
./mach test-tidy
</code>

Issues reported by test are to be fixed before pull request can be generated. This ensures that developers would adhere to coding standards. We have fixed all the issues reported by tidy. Further design patterns will be used in the next phase of the project, where validation functions will be implemented.

=='''Testing'''==
As of now, front-end UI testing is not possible as this requirement will be completely implemented during subsequent phases. However unit testing can be done by running following command

<code>
./mach test-wpt --release
</code>

There were 11 tests which were failing earlier but now these tests are passing. The expectation for these tests has been changed from FAIL to PASS. Further tests are only required for the next round where we will implement the methods for validation.

=='''Conclusion'''==
As a result of these initial changes, currently validation of the form elements has a basic implementation of the code required. The enum “ValidityStatus” is used to identify different states for the element. For each element in the form, the flow goes in this manner - First the “as_maybe_validatable” method in the element.rs file is called, which in turn finds out the type of the element and then calls the “is_instance_validatable” method on that element. In next phase of project, actual validation would be performed on list of Validatable elements. The state of the element depending upon the validation checks is one of the possible values in the enum. If the element validates all the possible checks, the state of the element is recorded as valid, else the state is either ValueMissing or one of the remaining enums in ValidityStatus. This state is recorded in the "state" variable in the ValidityState struct.

=='''References'''==
1. https://doc.rust-lang.org/stable/book/ 
2. https://en.wikipedia.org/wiki/Rust_(programming_language) 
3. https://en.wikipedia.org/wiki/Servo_(layout_engine) 
4. https://github.com/servo/servo/wiki/Form-validation-student-project 
5. https://doc.rust-lang.org/book/ 
6. http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2015/Mozilla_Refactor_GLES2

CSC/ECE 517 Spring 2016 M1601 Implement HTML5 form validation

2016-04-04T05:07:53Z

Gsrajadh: /* Requirements */

''' Implementation of HTML5 form validation in servo'''

Servo is a prototype web browser engine being developed by Mozilla and written in the Rust language. This project implements [https://en.wikipedia.org/wiki/HTML5 HTML5] validations for servo. The validations are implemented via methods such as "valueMissing" which determine for different elements such a HTMLInput element etc. if it is ok to leave the input blank or if input is required. The code snippets given in this wiki explain how these methods are called in the HTML elements via different enums. The actual code to validate these inputs, will be implemented in the next phase of the project.

=='''Introduction'''==
The [https://en.wikipedia.org/wiki/HTML5 HTML5]is a markup language used for displaying content on the World Wide Web

HTML5 defines set of specification which users needs to follow to make web pages HTML5 compliant. HTML 5 defines a mechanism by which contents of forms can be validated before user is allowed to submit them. [https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] currently implements support for few of the form elements. This project is intended to implement client-side validations for these elements and extend the existing form element subset to include additional form elements that will support client side validation.

===Servo===
[https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] is an open source prototype web browser layout engine that is being developed by Mozilla Research. It is written in [https://www.rust-lang.org/ Rust] language. Current browser engines are mostly based on single-threaded model. Although there are some tasks (as decompressing images) which can be done on separate processor cores but most of the work (like interpreting HTML and laying out pages) is single-threaded.
Motivation behind servo is to create a highly parallel environment, where different components (such as rendering, layout, HTML parsing, image decoding, etc.) can be handled by fine-grained, isolated tasks.

===Rust===
[http://doc.rust-lang.org/book/README.html Rust] is an open source systems programming language developed by Mozilla Research. Rust is designed to provide the same level of performance and power as C++, but without the risk of bugs and security flaws, and also with built-in mechanisms for exploiting multi-core processors.

=='''Project Description'''==
Write some description here

===Compiling and Building Servo===
* The project requirement initially stated that we build and Compile servo. Following are the steps for this:
Servo is built with [https://mail.mozilla.org/pipermail/rust-dev/2014-March/009090.html Cargo], the Rust package manager. Mozilla's Mach tools are used to orchestrate the build and other tasks.

git clone https://github.com/servo/servo
cd servo
./mach build --dev
./mach run tests/html/about-mozilla.html

===Steps Completed During Last Phase===
* The first requirement was to uncomment the attributes in ValidityState.weidl and fix the resulting build errors by implementing appropriate stub methods in validitystate.rs. This facilitates in declaring the methods which we will be using for validation
* Next, we had to modify the ValidityState constructor to take an &Element argument and store it as element variable of JS<Element> type member in the ValidityState.
* The changes to the constructor resulted in build errors in following files as the constructor was referred to in these files
So, the constructors called in these files were modified to send the required extra parameter.
* Next, we had to add a new enum “ValidityStatus” in ValidityState having each possible validity check in ValidityState. This enum is used to specify the state in order to describe if there is a Value missing or if there is no error and the state is valid
* Next, we had to define a new trait Validatable having method “is_instance_validatable”. (which takes the new ValidityStatus enum as an argument.)
* Next, we implemented this trait and the corresponding method in the following files
* Then, we had to define method as_maybe_validatable in file “element.rs” which returns an &Validatable value if the element implements the newly defined trait. This is used to check if the element is infact validatable before performing further operations to check the form validations
* Finally, we added a new html file “form_html5_validations.html” to test the HTML5 validation for the mentioned conditions

==Requirements==
Our project requirement was to implement client side form validation and extend the supported subset of defined form elements. In order to implement this we were required to implement the following steps:
===Initial Steps===
* We were required to compile Servo and ensure that it runs on tests/html/about-mozilla.html
* Our next requirement was to uncomment the attributes in ValidityState.webidl and implement appropriate stub methods in validitystate.rs in order to fix build errors
*We had to make the ValidityState constructor take an &Element argument and store it as a JS<Element> member in ValidityState
* We had to add a new enum that represents each possible validity check in ValidityState
* We had to define a Validatable trait that contains a method which accepts this enum as an argument
* Implement Validatable trait for the form element types
* We had to use the newly-added JS<Element> member to call the appropriate new methods in ValidityState

===Later Steps===
* Add a method to HTMLFormElement to statically validate form element constraints
* Add a method to HTMLFormElement to interactively validate the constraints of a form element
* We have to implement the checkValidity API and reportValidity API for HTMLFormElement
* We have to Implement each validity state by adding support for attributes such as min,max, minlength etc
* We need to modify the form submission algorithm to include constraint validation

==Design==
Blah blah
===Solution Overview===
* Create 3 lists 'control', 'invalid_control', 'unhadled_invalid-control'
* Initialize 'control' with all the submitted elements of the form.
* For each submitted element, check the elements for constraint validation and if check fails - add that element to 'invalid_control' list.
* If the 'invalid_control' list is empty return true.
* For each element in 'invalid_control' list, fire a simple event cancelable at field and if the event was not cancelled - add that element to 'unhadled_invalid-control' list.
* If the 'unhandled_invalid_control' list is empty return true.
* Return false along with the 'unhandled_invalid_control' list to the user_agent, which will focus on one or more of the reported issues to user for further action.

* Implements the validation methods in validitystate.rs
* Each method checks the element submitted to it for a particular constraint like value_missing, range_underflow etc and return false if the constraint check fails.
* Finally, the submit() method of form submission needs to be updated to invoke the interactive_validation() method.

method1: checkValidity
boolean,list<elements> static_validation(list<elements> control){

}

method2: reportValidity
boolean,list<elements> interactive_validation(list<elements> control){
//invoke method 1
status, unhandled_invalid_control = static_validation(control)

if (status==true)
return true, empty_list
else
return false, unhandled_invalid_control
}

===Validation Workflow===
Blah blah

===UML Diagram===
Blah blah

==='''Design Patterns & OO Practices'''===
We were not supposed to modify the existing design apart from adding a new behaviour/ability for HTML Element. We attempted to follow good OO practices throughout development. While using enums and also while defining new methods, we tried to follow the DRY principle in order to avoid repetition of code. Servo has it's own coding standards which are checked by running following command

<code>
./mach test-tidy
</code>

Issues reported by test are to be fixed before pull request can be generated. This ensures that developers would adhere to coding standards. We have fixed all the issues reported by tidy. Further design patterns will be used in the next phase of the project, where validation functions will be implemented.

=='''Testing'''==
As of now, front-end UI testing is not possible as this requirement will be completely implemented during subsequent phases. However unit testing can be done by running following command

<code>
./mach test-wpt --release
</code>

There were 11 tests which were failing earlier but now these tests are passing. The expectation for these tests has been changed from FAIL to PASS. Further tests are only required for the next round where we will implement the methods for validation.

=='''Conclusion'''==
As a result of these initial changes, currently validation of the form elements has a basic implementation of the code required. The enum “ValidityStatus” is used to identify different states for the element. For each element in the form, the flow goes in this manner - First the “as_maybe_validatable” method in the element.rs file is called, which in turn finds out the type of the element and then calls the “is_instance_validatable” method on that element. In next phase of project, actual validation would be performed on list of Validatable elements. The state of the element depending upon the validation checks is one of the possible values in the enum. If the element validates all the possible checks, the state of the element is recorded as valid, else the state is either ValueMissing or one of the remaining enums in ValidityStatus. This state is recorded in the "state" variable in the ValidityState struct.

=='''References'''==
1. https://doc.rust-lang.org/stable/book/ 
2. https://en.wikipedia.org/wiki/Rust_(programming_language) 
3. https://en.wikipedia.org/wiki/Servo_(layout_engine) 
4. https://github.com/servo/servo/wiki/Form-validation-student-project 
5. https://doc.rust-lang.org/book/ 
6. http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2015/Mozilla_Refactor_GLES2

CSC/ECE 517 Spring 2016/Functional tests for assignment creation function

2016-03-27T15:13:36Z

Gsrajadh: /* Setup */

=Functional tests for assignment creation function=
This page outlines the use tests for assignment creation using the Expertiza system
__TOC__

===Structural Overview===
Assignment creation in Expertiza provides a large number of options for users. Features come at the cost of complexity; this project is focused on creating testing methods to ensure that user interaction with the assignment interface remains stable and reliable.

Assignment creation is available from the Manage -> Assignments drop down on the expertiza site. Once an assignment is created it has 5 tabs for form entry. The remainder of this document will cover testing for each tab in more detail, the tabs are:
* General
* Topics
* Rubrics
* Review Strategy

Check the panxing01/expertiza repository for the current development files. Currently all tests are run in two files:
* https://github.com/panxing01/expertiza/blob/master/spec/features/assignment_create_spec.rb
* https://github.com/panxing01/expertiza/blob/master/spec/features/assignment_interface_spec.rb

===Class Hierarchy===
The Assignment class has many questionnaires throught the AssignmentQuestionnairs class. The Questionnaire class inherits from ActiveRecord::Base and has 8 fields plus primary key and date entries. The fields are:
* name: The name of the questionnaire row
* instructor_id: The instuctor key linked to the row
* private: True if private questionnaire
* min_question_score
* max_question_score
* type: field showing subclass
* display_type
* instruction_loc: stores URL for questionnaire instruction

The Questionnaire class has 11 sub-classes. They are:
* Rubric
* CourseEvaluationQuestionnaire
* SurveyQuestionnaire
* BookmarkRatingQuestionnaire
* AuthorFeedbackQuestionnaire
* QuizQuestionnaire
* GlobalSurveyQuestionnaire
* Metasurvey
* ReviewQuestionnaire
* MetareviewQuestionnaire
* TeammateReviewQuestionnaire

===Setup===
To setup functionality testing of assignment creation feature we did the following steps:
*Created RSpec file in /spec/features/ folder of [https://github.com/expertiza/expertiza Expertiza]
* Wrote functional tests using [https://github.com/jnicklas/capybara Capybara]

===General===
In this section, the functional test includes assignment name, course, submission directory, description URL, "Has team?", "Has quiz?" and "Calibrated peer-review for training".
*assignment name
<pre>
it "can set assginment name" do
login_as("instructor6")
visit '/assignments/new?private=0'
expect(page).to have_content "Assignment name"
fill_in "Assignment name:", with: 'assignment for test'
click_button "Create"
expect(Assignment.where(name: "assignment for test")).to exist
end
</pre>
*course
<pre>
it "can select course" do
login_as("instructor6")
visit '/assignments/new?private=0'
select('5', :from => 'assignment_form_assignment_course_id')
click_button "Create"
end
</pre>
*submission directory
<pre>
it "can set assginment Submission directory" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 2'
expect(page).to have_content "Submission directory"
fill_in "Submission directory:", with: 'Submission directory for test'
click_button "Create"
expect(Assignment.find(2).directory_path).to eq 'Submission directory for test'
end
</pre>
*description URL
<pre>
it "can set assginment Description URL" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 3'
expect(page).to have_content "Description URL"
fill_in "Description URL:", with: 'Description URL for test'
click_button "Create"
expect(Assignment.find(2).spec_location).to eq 'Description URL for test'
end
</pre>
*"Has team?"
<pre>
it "can Has teams and set team number" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 5'
find('#team_assignment').set(true)
expect(page).to have_content "Maximum number of members per team"
expect(page).to have_content "Show teammate reviews"
fill_in 'assignment_form_assignment_max_team_size', with: 4
find('#assignment_form_assignment_show_teammate_reviews').set(true)
click_button "Create"
expect(Assignment.find(2).show_teammate_reviews).to eq true
end
</pre>
*"Has quiz?"
<pre>
it "can save the number of quiz questions" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: '11'
select('5', :from => 'assignment_form_assignment_course_id')
find('#assignment_form_assignment_require_quiz').set(true)
click_button "Create"
visit '/assignments/2/edit'
expect(page).to have_content "Number of Quiz questions"
end
</pre>
*"Calibrated peer-review for training"
<pre>
it "can set Calibrated peer-view for training" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 4'
find('#assignment_form_assignment_is_calibrated').set(true)
click_button "Create"
expect(Assignment.find(2).is_calibrated).to eq true
end
</pre>
===Topics===
In this section, functionality of "Edit topics" is thoroughly tested. Below are some of the code snippets of this testing module:
*Edit topics content
<pre>
it "is able to see edit topics content correctly" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'
expect(page).to have_content("Allow topic suggestions from students?")
expect(page).to have_content("Enable bidding for topics?")
expect(page).to have_content("Enable authors to review others working on same topic?")
expect(page).to have_content("Allow reviewer to choose which topic to review?")
expect(page).to have_content("Allow participants to create bookmarks? ")
expect(page).to have_content("Hide all teams")
expect(page).to have_content("New topic")
expect(page).to have_content("Import Topics")
expect(page).to have_content("Back")
expect(page).to have_content("Save")
end
</pre>

*Show/hide teams
<pre>
it "is able to show/hide teams" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'

click_link('Hide all teams')

expect(page).to have_content("Show all teams")

click_link("Show all teams")
expect(page).to have_content("Hide all teams")
end
</pre>

===Rubrics===
Rubrics are arranged into 3 rows of data named "Review", "Author Feedback", and "Teammate Review". Each row is handled under separate descriptions in order to allow quick and comprehensive testing for the seperate functions.
Each row updates using a subclass of the Questionnaire class for dropdown values. Classes used are the ReviewQuestionnaire, AuthorFeedbackQuestionnaire, and the TeammateReviewQuestionnaire respectively.

Testing required creation of the three questionnaire subclasses in order to populate the dropdowns. Basic code layout for testing each value change:
<pre>
describe "Edit [subclass] rubric" do
it "should update [component]", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("[table row identifier]") do
select "[subclass instance name value]", :from => '[form identifier]'
end
click_button 'Save'
expect([questionnaireinstance]).to have_attributes([attrib updated] => [new value])
end
</pre>
===Review Strategy===
In this module we have tested the functionality of the "Teammate Review" module. Some of the tests are given below:
*Teammate Review
<pre>
it "should update questionnaire", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2")).to exist
end
</pre>

*Notification limit
<pre>
it "should update notification limit", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
fill_in 'assignment_form[assignment_questionnaire][][notification_limit]', :with => '50'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2").first).to have_attributes(:notification_limit => 50)
end
</pre>

===Running the tests===
The tests can be run on the terminal using the command:
<pre>
rspec path/to/spec/file.rb
</pre>
We can check if the functionality of the system is implemented properly seeing if the corresponding tests pass or fail.

CSC/ECE 517 Spring 2016/Functional tests for assignment creation function

2016-03-27T15:12:30Z

Gsrajadh: /* Functional tests for assignment creation function */

=Functional tests for assignment creation function=
This page outlines the use tests for assignment creation using the Expertiza system
__TOC__

===Structural Overview===
Assignment creation in Expertiza provides a large number of options for users. Features come at the cost of complexity; this project is focused on creating testing methods to ensure that user interaction with the assignment interface remains stable and reliable.

Assignment creation is available from the Manage -> Assignments drop down on the expertiza site. Once an assignment is created it has 5 tabs for form entry. The remainder of this document will cover testing for each tab in more detail, the tabs are:
* General
* Topics
* Rubrics
* Review Strategy

Check the panxing01/expertiza repository for the current development files. Currently all tests are run in two files:
* https://github.com/panxing01/expertiza/blob/master/spec/features/assignment_create_spec.rb
* https://github.com/panxing01/expertiza/blob/master/spec/features/assignment_interface_spec.rb

===Class Hierarchy===
The Assignment class has many questionnaires throught the AssignmentQuestionnairs class. The Questionnaire class inherits from ActiveRecord::Base and has 8 fields plus primary key and date entries. The fields are:
* name: The name of the questionnaire row
* instructor_id: The instuctor key linked to the row
* private: True if private questionnaire
* min_question_score
* max_question_score
* type: field showing subclass
* display_type
* instruction_loc: stores URL for questionnaire instruction

The Questionnaire class has 11 sub-classes. They are:
* Rubric
* CourseEvaluationQuestionnaire
* SurveyQuestionnaire
* BookmarkRatingQuestionnaire
* AuthorFeedbackQuestionnaire
* QuizQuestionnaire
* GlobalSurveyQuestionnaire
* Metasurvey
* ReviewQuestionnaire
* MetareviewQuestionnaire
* TeammateReviewQuestionnaire

===Setup===
To setup functionality testing of assignment creation feature we did the following steps:
*Created RSpec file in /spec/features/ folder of [https://github.com/expertiza/expertiza Expertiza]
* Wrote functional tests using Capybara[https://github.com/jnicklas/capybara]

===General===
In this section, the functional test includes assignment name, course, submission directory, description URL, "Has team?", "Has quiz?" and "Calibrated peer-review for training".
*assignment name
<pre>
it "can set assginment name" do
login_as("instructor6")
visit '/assignments/new?private=0'
expect(page).to have_content "Assignment name"
fill_in "Assignment name:", with: 'assignment for test'
click_button "Create"
expect(Assignment.where(name: "assignment for test")).to exist
end
</pre>
*course
<pre>
it "can select course" do
login_as("instructor6")
visit '/assignments/new?private=0'
select('5', :from => 'assignment_form_assignment_course_id')
click_button "Create"
end
</pre>
*submission directory
<pre>
it "can set assginment Submission directory" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 2'
expect(page).to have_content "Submission directory"
fill_in "Submission directory:", with: 'Submission directory for test'
click_button "Create"
expect(Assignment.find(2).directory_path).to eq 'Submission directory for test'
end
</pre>
*description URL
<pre>
it "can set assginment Description URL" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 3'
expect(page).to have_content "Description URL"
fill_in "Description URL:", with: 'Description URL for test'
click_button "Create"
expect(Assignment.find(2).spec_location).to eq 'Description URL for test'
end
</pre>
*"Has team?"
<pre>
it "can Has teams and set team number" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 5'
find('#team_assignment').set(true)
expect(page).to have_content "Maximum number of members per team"
expect(page).to have_content "Show teammate reviews"
fill_in 'assignment_form_assignment_max_team_size', with: 4
find('#assignment_form_assignment_show_teammate_reviews').set(true)
click_button "Create"
expect(Assignment.find(2).show_teammate_reviews).to eq true
end
</pre>
*"Has quiz?"
<pre>
it "can save the number of quiz questions" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: '11'
select('5', :from => 'assignment_form_assignment_course_id')
find('#assignment_form_assignment_require_quiz').set(true)
click_button "Create"
visit '/assignments/2/edit'
expect(page).to have_content "Number of Quiz questions"
end
</pre>
*"Calibrated peer-review for training"
<pre>
it "can set Calibrated peer-view for training" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 4'
find('#assignment_form_assignment_is_calibrated').set(true)
click_button "Create"
expect(Assignment.find(2).is_calibrated).to eq true
end
</pre>
===Topics===
In this section, functionality of "Edit topics" is thoroughly tested. Below are some of the code snippets of this testing module:
*Edit topics content
<pre>
it "is able to see edit topics content correctly" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'
expect(page).to have_content("Allow topic suggestions from students?")
expect(page).to have_content("Enable bidding for topics?")
expect(page).to have_content("Enable authors to review others working on same topic?")
expect(page).to have_content("Allow reviewer to choose which topic to review?")
expect(page).to have_content("Allow participants to create bookmarks? ")
expect(page).to have_content("Hide all teams")
expect(page).to have_content("New topic")
expect(page).to have_content("Import Topics")
expect(page).to have_content("Back")
expect(page).to have_content("Save")
end
</pre>

*Show/hide teams
<pre>
it "is able to show/hide teams" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'

click_link('Hide all teams')

expect(page).to have_content("Show all teams")

click_link("Show all teams")
expect(page).to have_content("Hide all teams")
end
</pre>

===Rubrics===
Rubrics are arranged into 3 rows of data named "Review", "Author Feedback", and "Teammate Review". Each row is handled under separate descriptions in order to allow quick and comprehensive testing for the seperate functions.
Each row updates using a subclass of the Questionnaire class for dropdown values. Classes used are the ReviewQuestionnaire, AuthorFeedbackQuestionnaire, and the TeammateReviewQuestionnaire respectively.

Testing required creation of the three questionnaire subclasses in order to populate the dropdowns. Basic code layout for testing each value change:
<pre>
describe "Edit [subclass] rubric" do
it "should update [component]", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("[table row identifier]") do
select "[subclass instance name value]", :from => '[form identifier]'
end
click_button 'Save'
expect([questionnaireinstance]).to have_attributes([attrib updated] => [new value])
end
</pre>
===Review Strategy===
In this module we have tested the functionality of the "Teammate Review" module. Some of the tests are given below:
*Teammate Review
<pre>
it "should update questionnaire", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2")).to exist
end
</pre>

*Notification limit
<pre>
it "should update notification limit", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
fill_in 'assignment_form[assignment_questionnaire][][notification_limit]', :with => '50'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2").first).to have_attributes(:notification_limit => 50)
end
</pre>

===Running the tests===
The tests can be run on the terminal using the command:
<pre>
rspec path/to/spec/file.rb
</pre>
We can check if the functionality of the system is implemented properly seeing if the corresponding tests pass or fail.

CSC/ECE 517 Spring 2016/Functional tests for assignment creation function

2016-03-25T01:10:33Z

Gsrajadh: /* Setup */

=Functional tests for assignment creation function=
This page outlines the use tests for assignment creation using the Expertiza system
__TOC__

===Structural Overview===
Assignment creation in Expertiza provides a large number of options for users. Features come at the cost of complexity; this project is focused on creating testing methods to ensure that user interaction with the assignment interface remains stable and reliable.

Assignment creation is available from the Manage -> Assignments drop down on the expertiza site. Once an assignment is created it has 5 tabs for form entry. The remainder of this document will cover testing for each tab in more detail, the tabs are:
* General
* Topics
* Rubrics
* Review Strategy

===Setup===
To setup functionality testing of assignment creation feature we did the following steps:
*Created RSpec file in /spec/features/ folder of [https://github.com/expertiza/expertiza Expertiza]
* Wrote functional tests using Capybara

===General===
In this section, the functional test includes assignment name, course, submission directory, description URL, "Has team?", "Has quiz?" and "Calibrated peer-review for training".
*assignment name
<pre>
it "can set assginment name" do
login_as("instructor6")
visit '/assignments/new?private=0'
expect(page).to have_content "Assignment name"
fill_in "Assignment name:", with: 'assignment for test'
click_button "Create"
expect(Assignment.where(name: "assignment for test")).to exist
end
</pre>
*course
<pre>
it "can select course" do
login_as("instructor6")
visit '/assignments/new?private=0'
select('5', :from => 'assignment_form_assignment_course_id')
click_button "Create"
end
</pre>
*submission directory
<pre>
it "can set assginment Submission directory" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 2'
expect(page).to have_content "Submission directory"
fill_in "Submission directory:", with: 'Submission directory for test'
click_button "Create"
expect(Assignment.find(2).directory_path).to eq 'Submission directory for test'
end
</pre>
*description URL
<pre>
it "can set assginment Description URL" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 3'
expect(page).to have_content "Description URL"
fill_in "Description URL:", with: 'Description URL for test'
click_button "Create"
expect(Assignment.find(2).spec_location).to eq 'Description URL for test'
end
</pre>
*"Has team?"
<pre>
it "can Has teams and set team number" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 5'
find('#team_assignment').set(true)
expect(page).to have_content "Maximum number of members per team"
expect(page).to have_content "Show teammate reviews"
fill_in 'assignment_form_assignment_max_team_size', with: 4
find('#assignment_form_assignment_show_teammate_reviews').set(true)
click_button "Create"
expect(Assignment.find(2).show_teammate_reviews).to eq true
end
</pre>
*"Has quiz?"
<pre>
it "can save the number of quiz questions" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: '11'
select('5', :from => 'assignment_form_assignment_course_id')
find('#assignment_form_assignment_require_quiz').set(true)
click_button "Create"
visit '/assignments/2/edit'
expect(page).to have_content "Number of Quiz questions"
end
</pre>
*"Calibrated peer-review for training"
<pre>
it "can set Calibrated peer-view for training" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 4'
find('#assignment_form_assignment_is_calibrated').set(true)
click_button "Create"
expect(Assignment.find(2).is_calibrated).to eq true
end
</pre>
===Topics===
In this section, functionality of "Edit topics" is thoroughly tested. Below are some of the code snippets of this testing module:
*Edit topics content
<pre>
it "is able to see edit topics content correctly" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'
expect(page).to have_content("Allow topic suggestions from students?")
expect(page).to have_content("Enable bidding for topics?")
expect(page).to have_content("Enable authors to review others working on same topic?")
expect(page).to have_content("Allow reviewer to choose which topic to review?")
expect(page).to have_content("Allow participants to create bookmarks? ")
expect(page).to have_content("Hide all teams")
expect(page).to have_content("New topic")
expect(page).to have_content("Import Topics")
expect(page).to have_content("Back")
expect(page).to have_content("Save")
end
</pre>

*Show/hide teams
<pre>
it "is able to show/hide teams" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'

click_link('Hide all teams')

expect(page).to have_content("Show all teams")

click_link("Show all teams")
expect(page).to have_content("Hide all teams")
end
</pre>

===Rubrics===
Rubrics are arranged into 3 rows of data named "Review", "Author Feedback", and "Teammate Review". Each row is handled under separate descriptions in order to allow quick and comprehensive testing for the seperate functions.
Each row updates a subclass of the Questionnaire class. The Active Record hierarchy is:
* Questionnaire
** ReviewQuestionnaire
** AuthorFeedbackQuestionnaire
** TeammateReviewQuestionaire

The Questionnaire class is connected to the Assignment class via the AssignmentQuestionnaire class.

===Review Strategy===
In this module we have tested the functionality of the "Teammate Review" module. Some of the tests are given below:
*Teammate Review
<pre>
it "should update questionnaire", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2")).to exist
end
</pre>

*Notification limit
<pre>
it "should update notification limit", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
fill_in 'assignment_form[assignment_questionnaire][][notification_limit]', :with => '50'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2").first).to have_attributes(:notification_limit => 50)
end
</pre>

CSC/ECE 517 Spring 2016/Functional tests for assignment creation function

2016-03-25T01:07:22Z

Gsrajadh: /* Functional tests for assignment creation function */

=Functional tests for assignment creation function=
This page outlines the use tests for assignment creation using the Expertiza system
__TOC__

===Structural Overview===
Assignment creation in Expertiza provides a large number of options for users. Features come at the cost of complexity; this project is focused on creating testing methods to ensure that user interaction with the assignment interface remains stable and reliable.

Assignment creation is available from the Manage -> Assignments drop down on the expertiza site. Once an assignment is created it has 5 tabs for form entry. The remainder of this document will cover testing for each tab in more detail, the tabs are:
* General
* Topics
* Rubrics
* Review Strategy

===Setup===
To setup functionality testing of assignment creation feature we did the following steps:
*Created RSpec file in /spec/features/ folder of https://github.com/expertiza/expertiza
* Wrote functional tests using Capybara

===General===
In this section, the functional test includes assignment name, course, submission directory, description URL, "Has team?", "Has quiz?" and "Calibrated peer-review for training".
*assignment name
<pre>
it "can set assginment name" do
login_as("instructor6")
visit '/assignments/new?private=0'
expect(page).to have_content "Assignment name"
fill_in "Assignment name:", with: 'assignment for test'
click_button "Create"
expect(Assignment.where(name: "assignment for test")).to exist
end
</pre>
*course
<pre>
it "can select course" do
login_as("instructor6")
visit '/assignments/new?private=0'
select('5', :from => 'assignment_form_assignment_course_id')
click_button "Create"
end
</pre>
*submission directory
<pre>
it "can set assginment Submission directory" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 2'
expect(page).to have_content "Submission directory"
fill_in "Submission directory:", with: 'Submission directory for test'
click_button "Create"
expect(Assignment.find(2).directory_path).to eq 'Submission directory for test'
end
</pre>
*description URL
<pre>
it "can set assginment Description URL" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 3'
expect(page).to have_content "Description URL"
fill_in "Description URL:", with: 'Description URL for test'
click_button "Create"
expect(Assignment.find(2).spec_location).to eq 'Description URL for test'
end
</pre>
*"Has team?"
<pre>
it "can Has teams and set team number" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 5'
find('#team_assignment').set(true)
expect(page).to have_content "Maximum number of members per team"
expect(page).to have_content "Show teammate reviews"
fill_in 'assignment_form_assignment_max_team_size', with: 4
find('#assignment_form_assignment_show_teammate_reviews').set(true)
click_button "Create"
expect(Assignment.find(2).show_teammate_reviews).to eq true
end
</pre>
*"Has quiz?"
<pre>
it "can save the number of quiz questions" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: '11'
select('5', :from => 'assignment_form_assignment_course_id')
find('#assignment_form_assignment_require_quiz').set(true)
click_button "Create"
visit '/assignments/2/edit'
expect(page).to have_content "Number of Quiz questions"
end
</pre>
*"Calibrated peer-review for training"
<pre>
it "can set Calibrated peer-view for training" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 4'
find('#assignment_form_assignment_is_calibrated').set(true)
click_button "Create"
expect(Assignment.find(2).is_calibrated).to eq true
end
</pre>
===Topics===
In this section, functionality of "Edit topics" is thoroughly tested. Below are some of the code snippets of this testing module:
*Edit topics content
<pre>
it "is able to see edit topics content correctly" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'
expect(page).to have_content("Allow topic suggestions from students?")
expect(page).to have_content("Enable bidding for topics?")
expect(page).to have_content("Enable authors to review others working on same topic?")
expect(page).to have_content("Allow reviewer to choose which topic to review?")
expect(page).to have_content("Allow participants to create bookmarks? ")
expect(page).to have_content("Hide all teams")
expect(page).to have_content("New topic")
expect(page).to have_content("Import Topics")
expect(page).to have_content("Back")
expect(page).to have_content("Save")
end
</pre>

*Show/hide teams
<pre>
it "is able to show/hide teams" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'

click_link('Hide all teams')

expect(page).to have_content("Show all teams")

click_link("Show all teams")
expect(page).to have_content("Hide all teams")
end
</pre>

===Rubrics===
Rubrics are arranged into 3 rows of data named "Review", "Author Feedback", and "Teammate Review". Each row is handled under separate descriptions in order to allow quick and comprehensive testing for the seperate functions.
Each row updates a subclass of the Questionnaire class. The Active Record hierarchy is:
* Questionnaire
** ReviewQuestionnaire
** AuthorFeedbackQuestionnaire
** TeammateReviewQuestionaire

The Questionnaire class is connected to the Assignment class via the AssignmentQuestionnaire class.

===Review Strategy===
In this module we have tested the functionality of the "Teammate Review" module. Some of the tests are given below:
*Teammate Review
<pre>
it "should update questionnaire", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2")).to exist
end
</pre>

*Notification limit
<pre>
it "should update notification limit", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
fill_in 'assignment_form[assignment_questionnaire][][notification_limit]', :with => '50'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2").first).to have_attributes(:notification_limit => 50)
end
</pre>

CSC/ECE 517 Spring 2016/Functional tests for assignment creation function

2016-03-25T01:03:33Z

Gsrajadh: /* Due dates */

=Functional tests for assignment creation function=
This page outlines the use tests for assignment creation using the Expertiza system
__TOC__

===Structural Overview===
Assignment creation in Expertiza provides a large number of options for users. Features come at the cost of complexity; this project is focused on creating testing methods to ensure that user interaction with the assignment interface remains stable and reliable.

Assignment creation is available from the Manage -> Assignments drop down on the expertiza site. Once an assignment is created it has 5 tabs for form entry. The remainder of this document will cover testing for each tab in more detail, the tabs are:
* General
* Topics
* Rubrics
* Review Strategy

===General===
In this section, the functional test includes assignment name, course, submission directory, description URL, "Has team?", "Has quiz?" and "Calibrated peer-review for training".
*assignment name
<pre>
it "can set assginment name" do
login_as("instructor6")
visit '/assignments/new?private=0'
expect(page).to have_content "Assignment name"
fill_in "Assignment name:", with: 'assignment for test'
click_button "Create"
expect(Assignment.where(name: "assignment for test")).to exist
end
</pre>
*course
<pre>
it "can select course" do
login_as("instructor6")
visit '/assignments/new?private=0'
select('5', :from => 'assignment_form_assignment_course_id')
click_button "Create"
end
</pre>
*submission directory
<pre>
it "can set assginment Submission directory" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 2'
expect(page).to have_content "Submission directory"
fill_in "Submission directory:", with: 'Submission directory for test'
click_button "Create"
expect(Assignment.find(2).directory_path).to eq 'Submission directory for test'
end
</pre>
*description URL
<pre>
it "can set assginment Description URL" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 3'
expect(page).to have_content "Description URL"
fill_in "Description URL:", with: 'Description URL for test'
click_button "Create"
expect(Assignment.find(2).spec_location).to eq 'Description URL for test'
end
</pre>
*"Has team?"
<pre>
it "can Has teams and set team number" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 5'
find('#team_assignment').set(true)
expect(page).to have_content "Maximum number of members per team"
expect(page).to have_content "Show teammate reviews"
fill_in 'assignment_form_assignment_max_team_size', with: 4
find('#assignment_form_assignment_show_teammate_reviews').set(true)
click_button "Create"
expect(Assignment.find(2).show_teammate_reviews).to eq true
end
</pre>
*"Has quiz?"
<pre>
it "can save the number of quiz questions" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: '11'
select('5', :from => 'assignment_form_assignment_course_id')
find('#assignment_form_assignment_require_quiz').set(true)
click_button "Create"
visit '/assignments/2/edit'
expect(page).to have_content "Number of Quiz questions"
end
</pre>
*"Calibrated peer-review for training"
<pre>
it "can set Calibrated peer-view for training" do
login_as("instructor6")
visit '/assignments/new?private=0'
fill_in "Assignment name:", with: 'assignment for test 4'
find('#assignment_form_assignment_is_calibrated').set(true)
click_button "Create"
expect(Assignment.find(2).is_calibrated).to eq true
end
</pre>
===Topics===
In this section, functionality of "Edit topics" is thoroughly tested. Below are some of the code snippets of this testing module:
*Edit topics content
<pre>
it "is able to see edit topics content correctly" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'
expect(page).to have_content("Allow topic suggestions from students?")
expect(page).to have_content("Enable bidding for topics?")
expect(page).to have_content("Enable authors to review others working on same topic?")
expect(page).to have_content("Allow reviewer to choose which topic to review?")
expect(page).to have_content("Allow participants to create bookmarks? ")
expect(page).to have_content("Hide all teams")
expect(page).to have_content("New topic")
expect(page).to have_content("Import Topics")
expect(page).to have_content("Back")
expect(page).to have_content("Save")
end
</pre>

*Show/hide teams
<pre>
it "is able to show/hide teams" do
login_as("instructor6")
visit 'assignments/1/edit#tab-2'

click_link('Hide all teams')

expect(page).to have_content("Show all teams")

click_link("Show all teams")
expect(page).to have_content("Hide all teams")
end
</pre>

===Rubrics===
Rubrics are arranged into 3 rows of data named "Review", "Author Feedback", and "Teammate Review". Each row is handled under separate descriptions in order to allow quick and comprehensive testing for the seperate functions.
Each row updates a subclass of the Questionnaire class. The Active Record hierarchy is:
* Questionnaire
** ReviewQuestionnaire
** AuthorFeedbackQuestionnaire
** TeammateReviewQuestionaire

The Questionnaire class is connected to the Assignment class via the AssignmentQuestionnaire class.

===Review Strategy===
In this module we have tested the functionality of the "Teammate Review" module. Some of the tests are given below:
*Teammate Review
<pre>
it "should update questionnaire", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2")).to exist
end
</pre>

*Notification limit
<pre>
it "should update notification limit", js: true do
login_as("instructor6")
visit '/assignments/1/edit'
find_link('Rubrics').click
within("tr#questionnaire_table_TeammateReviewQuestionnaire") do
select "TeammateReviewQuestionnaire2", :from => 'assignment_form[assignment_questionnaire][][questionnaire_id]'
fill_in 'assignment_form[assignment_questionnaire][][notification_limit]', :with => '50'
end
click_button 'Save'
expect(get_questionnaire("TeammateReviewQuestionnaire2").first).to have_attributes(:notification_limit => 50)
end
</pre>

CSC/ECE 517 Spring 2016/Functional tests for assignment creation function

2016-03-25T01:00:18Z

Gsrajadh: /* Topics */

CSC/ECE 517 Spring 2016/Functional tests for assignment creation function

2016-03-25T00:57:52Z

Gsrajadh: /* Topics */

CSC/ECE 517 Spring 2016/Functional tests for assignment creation function

2016-03-25T00:56:00Z

Gsrajadh: /* Structural Overview */