Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2017/E17A2 Lightweight Badging System

2017-11-07T00:45:10Z

Pjain15: /* Requirement Specification */

= Problem Statement=
To create a simple badging system for Expertiza such that the students can be badged when certain criteria are matched.

Badging feature allows students to be badged on expertiza based on the matching of certain criteria. ‘Good Reviewer’ and ‘Good Teammate’ badges can be given to students based on the scores given to them by instructors or the other teammates.

A ‘Good Reviewer’ badge is assigned when a student gets review score of more than a particular threshold or more than 95 by default.
Similarly, a 'Good teammate' badge is assigned when the teammate review score is greater than a particular threshold, defaulted to 95.
The criterion to receive the badges are configurable for the instructors and can be changed for different tasks and assignments.

=Requirement Specification=
1.Creating badges for 'Good Reviewer' and 'Good Teammate' 
2 Create a table named “badges” where the badges and their description can be stored.
 3.Create a mapping table named “assignment_badges”, for mapping badges with assignments and storing the specific thresholds
 4.Create a mapping table named “awarded_badges”, to map student with badges.
 5.Providing means to configure the badging criteria by adding 'Calibration' tab in Assignments/edit page.
 6.Adding badges in student/task list to allow the viewing of badges associated with students.
 7.Adding badges to participants/list for an instructor to view.
 8.Implement feature tests to verify the new feature addition.
 9.Adding hover feature on each badge to allow the viewer to read the description of the badge without taking up column width or height.

= Team Contact =

; MEMBERS:

:Priyanka Jain: [mailto:pjain15@ncsu.edu pjain15@ncsu.edu]

:Pushpendra Patel: [mailto:ppatel16@ncsu.edu ppatel16@ncsu.edu]

:Tanay Kothari: [mailto:tkothar@ncsu.edu tkothar@ncsu.edu]

:Timothy Dement: [mailto:tmdement@ncsu.edu tmdement@ncsu.edu]

; MENTOR:

:Zhewei Hu: [mailto:zhu6@ncsu.edu zhu6@ncsu.edu]

CSC/ECE 517 Fall 2017/E17A2 Lightweight Badging System

2017-11-07T00:41:47Z

Pjain15: /* Problem Statement */

= Problem Statement=
To create a simple badging system for Expertiza such that the students can be badged when certain criteria are matched.

Badging feature allows students to be badged on expertiza based on the matching of certain criteria. ‘Good Reviewer’ and ‘Good Teammate’ badges can be given to students based on the scores given to them by instructors or the other teammates.

A ‘Good Reviewer’ badge is assigned when a student gets review score of more than a particular threshold or more than 95 by default.
Similarly, a 'Good teammate' badge is assigned when the teammate review score is greater than a particular threshold, defaulted to 95.
The criterion to receive the badges are configurable for the instructors and can be changed for different tasks and assignments.

=Requirement Specification=
1.Creating badges for 'Good Reviewer' and 'Good Teammate' 
2 Create a table named “badges” where the badges and their description can be stored.
 3.Create a mapping table named “assignment_badges”, for mapping badges with assignments and storing the specific thresholds
 4.Create a mapping table named “awarded_badges”, to map student with badges.
 5.Providing means to configure the badging criteria by adding 'Calibration' tab in Assignments/edit page.
 6.Adding badges in student/task list to allow the viewing of badges associated with students.
 7.Adding badges to participants/list for an instructor to view.
 8.Implement feature tests to verify the new feature addition.

= Team Contact =

; MEMBERS:

:Priyanka Jain: [mailto:pjain15@ncsu.edu pjain15@ncsu.edu]

:Pushpendra Patel: [mailto:ppatel16@ncsu.edu ppatel16@ncsu.edu]

:Tanay Kothari: [mailto:tkothar@ncsu.edu tkothar@ncsu.edu]

:Timothy Dement: [mailto:tmdement@ncsu.edu tmdement@ncsu.edu]

; MENTOR:

:Zhewei Hu: [mailto:zhu6@ncsu.edu zhu6@ncsu.edu]

CSC/ECE 517 Fall 2017/E17A2 Lightweight Badging System

2017-11-06T23:57:01Z

Pjain15: /* Problem Statement */

CSC/ECE 517 Fall 2017/E17A2 Lightweight Badging System

2017-11-06T23:56:34Z

Pjain15:

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-11-03T04:22:09Z

Pjain15: /* Results */

== Introduction ==

Expertiza is a web application which provides a dashboard to the students where they can submit and peer-review assignments, projects, codes, and other such objects. It allows students to review each other’s work and improve their work upon this feedback. Rubric advice allows reviewers to see what characteristics of work merit a particular score.

== The problem statement ==

Rubric advice lets a user see what criterion or characteristics of work merit a particular score. An instructor can retrieve peer review assignments and leave some advice or give scores based on some criteria. Similarly, students can log in and retrieve the rubric advice left by the instructor. We mocked the behavior of the user (both as an instructor and student) to see how different scenarios work, like modifying, saving and retrieving advice and building feature tests for it. The testing frameworks used for the same were Selenium and Capybara.

== Test Plan ==

An instructor when creating a questionnaire, can associate marks with comments which can enable a student to understand what score is appropriate for a particular work.
An instructor can subsequently edit or delete an advice.
A student can view and use this rubric advice when peer reviewing other's work.
Thus the test cases formed check if an instructor is able to:

* Create a questionnaire
* Edit or delete an advice
Creating a rubric advice has not been added as a test case because both edit and delete advice make an instructor 'create' an advice. An additional test case to do the same would have slowed down the testing process and hence is not advisable.

'''Student Side:'''
A student, when filling a peer review should be able to see the rubric advice associated with a particular test score. We test this task through adding a test case in the peer_review_spec.rb since Peer Review is superset of the Rubric Advice feature as it is a task where a student uses the rubric advice and submit it.

Files changed: peer_review_spec.rb
The test case checks if student is able to select a rubric advice that the instructor has created and then submit it.
<pre>
it "able to view and use rubric advice", :js => true do
load_questionnaire
expect(page).to have_content "Show advice"
page.find('#showAdivce_1').click
expect(page).to have_content "5 - Good"
page.find("a", :text => "5 - Good").click
click_button "Save Review"
expect(page).to have_content "Your response was successfully saved."
end
</pre>

The existing code given creates the required environment for the test student. It sets up a team, assignment and other required elements for the test student to submit a review.
<pre>
before(:each) do
create(:assignment, name: "TestAssignment", directory_path: 'test_assignment')
create_list(:participant, 3)
create(:assignment_node)
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: 'review').first, due_at: Time.now.in_time_zone + 1.day)
create(:topic)
create(:topic, topic_name: "TestReview")
create(:team_user, user: User.where(role_id: 2).first)
create(:team_user, user: User.where(role_id: 2).second)
create(:assignment_team)
create(:team_user, user: User.where(role_id: 2).third, team: AssignmentTeam.second)
create(:signed_up_team)
create(:signed_up_team, team_id: 2, topic: SignUpTopic.second)
create(:assignment_questionnaire)
create(:question)
create(:question_advices)
end
</pre>

The rubric advice is prepared in factory.rb with the following code addition . This allows our test Student to get a ready rubric advice that he can choose.
<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

'''Instructor side:'''

Edit a certain review rubric, and add advice to it.
Test that when advice is added for a particular criterion, the advice can be retrieved and that it is exactly the advice that was added. Files added: review_rubric_spec.rb

<pre>
describe "Edit a rubric advice" do
it "is able to edit a review rubric advice" do
# creating a new rubric advice
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
# setting intital advice in the field
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# editing a review rubric - Setting any element with new data
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Edited the advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Edited the advice')
end
end

describe "Remove a rubric advice" do
it "should be able to delete a rubric advice" do
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# edit review advice to set to blank i.e. delete rubric advice
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
end
end
end
</pre>

Apart from the major test case for Rubric advice, it is essential to test if the logged in instructor is an authorized instructor. To test this, we have added the following test in review_rubric_spec.rb.
Also, the task of loading the questionnaire and the question types is implemented in separate methods to allow reuse.

<pre>

include InstructorInterfaceHelperSpec

# Feature test of rubric advice
describe "Edit rubric advice" do
before(:each) do
assignment_setup
end

# Login test
describe "Login as instructor" do
it "logs in with valid username and password" do
login_as("instructor6")
visit '/tree_display/list'
expect(page).to have_content("Manage content")
end

it "logs in with invalid username and password" do
visit root_path
fill_in 'login_name', with: 'instructor6'
fill_in 'login_password', with: 'wrongpassword'
click_button 'SIGN IN'
expect(page).to have_text('Your username or password is incorrect.')
end
end

def load_questionnaire
login_as("instructor6")
visit '/questionnaires/new?model=ReviewQuestionnaire&private=0'
fill_in('questionnaire_name', with: 'DummyReview')
fill_in('questionnaire_min_question_score', with: '0')
fill_in('questionnaire_max_question_score', with: '5')
select('no', from: 'questionnaire_private')
click_button "Create"
end

def load_question question_type
load_questionnaire
fill_in('question_total_num', with: '1')
select(question_type, from: 'question_type')
click_button "Add"
end
</pre>

'''Factories.rb'''

<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

It associates a merit score with each type of advice. As an example, 5 denotes 'very good'.

== Results ==

* [https://youtu.be/0a5FUXhJHBQ Demo Video of Testing]
* Build passing with Coverage increase of +0.3%

[[File:coverage.jpg]][[File:BuildPass1.jpg]]

== Testing Instructions ==
* [https://github.com/expertiza/expertiza Clone Expertiza on local Repository]
* [http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation#Development_Environment_Setup_Guides Setup expertiza on your local machine]
* Run the test cases:
<pre>spec/features/peer_review_spec.rb </pre>
<pre>spec/features/review_rubric_spec.rb using [https://relishapp.com/rspec Rspec]</pre>

== References ==

* [https://github.com/rcoutin/expertiza Forked Github Expertiza Repository]
* [https://github.com/expertiza/expertiza Github Expertiza Repository]
* [https://relishapp.com/rspec Rspec Documentation]

File:BuildPass1.jpg

2017-11-03T04:21:13Z

Pjain15: Travis Build Pass

Travis Build Pass

File:BuildPass.JPG

2017-11-03T04:16:56Z

Pjain15:

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-11-03T04:15:27Z

Pjain15:

== Introduction ==

Expertiza is a web application which provides a dashboard to the students where they can submit and peer-review assignments, projects, codes, and other such objects. It allows students to review each other’s work and improve their work upon this feedback. Rubric advice allows reviewers to see what characteristics of work merit a particular score.

== The problem statement ==

Rubric advice lets a user see what criterion or characteristics of work merit a particular score. An instructor can retrieve peer review assignments and leave some advice or give scores based on some criteria. Similarly, students can log in and retrieve the rubric advice left by the instructor. We mocked the behavior of the user (both as an instructor and student) to see how different scenarios work, like modifying, saving and retrieving advice and building feature tests for it. The testing frameworks used for the same were Selenium and Capybara.

== Test Plan ==

An instructor when creating a questionnaire, can associate marks with comments which can enable a student to understand what score is appropriate for a particular work.
An instructor can subsequently edit or delete an advice.
A student can view and use this rubric advice when peer reviewing other's work.
Thus the test cases formed check if an instructor is able to:

* Create a questionnaire
* Edit or delete an advice
Creating a rubric advice has not been added as a test case because both edit and delete advice make an instructor 'create' an advice. An additional test case to do the same would have slowed down the testing process and hence is not advisable.

'''Student Side:'''
A student, when filling a peer review should be able to see the rubric advice associated with a particular test score. We test this task through adding a test case in the peer_review_spec.rb since Peer Review is superset of the Rubric Advice feature as it is a task where a student uses the rubric advice and submit it.

Files changed: peer_review_spec.rb
The test case checks if student is able to select a rubric advice that the instructor has created and then submit it.
<pre>
it "able to view and use rubric advice", :js => true do
load_questionnaire
expect(page).to have_content "Show advice"
page.find('#showAdivce_1').click
expect(page).to have_content "5 - Good"
page.find("a", :text => "5 - Good").click
click_button "Save Review"
expect(page).to have_content "Your response was successfully saved."
end
</pre>

The existing code given creates the required environment for the test student. It sets up a team, assignment and other required elements for the test student to submit a review.
<pre>
before(:each) do
create(:assignment, name: "TestAssignment", directory_path: 'test_assignment')
create_list(:participant, 3)
create(:assignment_node)
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: 'review').first, due_at: Time.now.in_time_zone + 1.day)
create(:topic)
create(:topic, topic_name: "TestReview")
create(:team_user, user: User.where(role_id: 2).first)
create(:team_user, user: User.where(role_id: 2).second)
create(:assignment_team)
create(:team_user, user: User.where(role_id: 2).third, team: AssignmentTeam.second)
create(:signed_up_team)
create(:signed_up_team, team_id: 2, topic: SignUpTopic.second)
create(:assignment_questionnaire)
create(:question)
create(:question_advices)
end
</pre>

The rubric advice is prepared in factory.rb with the following code addition . This allows our test Student to get a ready rubric advice that he can choose.
<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

'''Instructor side:'''

Edit a certain review rubric, and add advice to it.
Test that when advice is added for a particular criterion, the advice can be retrieved and that it is exactly the advice that was added. Files added: review_rubric_spec.rb

<pre>
describe "Edit a rubric advice" do
it "is able to edit a review rubric advice" do
# creating a new rubric advice
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
# setting intital advice in the field
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# editing a review rubric - Setting any element with new data
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Edited the advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Edited the advice')
end
end

describe "Remove a rubric advice" do
it "should be able to delete a rubric advice" do
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# edit review advice to set to blank i.e. delete rubric advice
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
end
end
end
</pre>

Apart from the major test case for Rubric advice, it is essential to test if the logged in instructor is an authorized instructor. To test this, we have added the following test in review_rubric_spec.rb.
Also, the task of loading the questionnaire and the question types is implemented in separate methods to allow reuse.

<pre>

include InstructorInterfaceHelperSpec

# Feature test of rubric advice
describe "Edit rubric advice" do
before(:each) do
assignment_setup
end

# Login test
describe "Login as instructor" do
it "logs in with valid username and password" do
login_as("instructor6")
visit '/tree_display/list'
expect(page).to have_content("Manage content")
end

it "logs in with invalid username and password" do
visit root_path
fill_in 'login_name', with: 'instructor6'
fill_in 'login_password', with: 'wrongpassword'
click_button 'SIGN IN'
expect(page).to have_text('Your username or password is incorrect.')
end
end

def load_questionnaire
login_as("instructor6")
visit '/questionnaires/new?model=ReviewQuestionnaire&private=0'
fill_in('questionnaire_name', with: 'DummyReview')
fill_in('questionnaire_min_question_score', with: '0')
fill_in('questionnaire_max_question_score', with: '5')
select('no', from: 'questionnaire_private')
click_button "Create"
end

def load_question question_type
load_questionnaire
fill_in('question_total_num', with: '1')
select(question_type, from: 'question_type')
click_button "Add"
end
</pre>

'''Factories.rb'''

<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

It associates a merit score with each type of advice. As an example, 5 denotes 'very good'.

== Results ==

* [https://youtu.be/0a5FUXhJHBQ Demo Video of Testing]
* Build passing with Coverage increase of +0.3%

[[File:coverage.jpg]][[File:BuildPass.jpg]]

== Testing Instructions ==
* [https://github.com/expertiza/expertiza Clone Expertiza on local Repository]
* [http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation#Development_Environment_Setup_Guides Setup expertiza on your local machine]
* Run the test cases:
<pre>spec/features/peer_review_spec.rb </pre>
<pre>spec/features/review_rubric_spec.rb using [https://relishapp.com/rspec Rspec]</pre>

== References ==

* [https://github.com/rcoutin/expertiza Forked Github Expertiza Repository]
* [https://github.com/expertiza/expertiza Github Expertiza Repository]
* [https://relishapp.com/rspec Rspec Documentation]

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-11-03T04:04:48Z

Pjain15: /* Test Plan */

== Introduction ==

Expertiza is a web application which provides a dashboard to the students where they can submit and peer-review assignments, projects, codes, and other such objects. It allows students to review each other’s work and improve their work upon this feedback. Rubric advice allows reviewers to see what characteristics of work merit a particular score.

== The problem statement ==

Rubric advice lets a user see what criterion or characteristics of work merit a particular score. An instructor can retrieve peer review assignments and leave some advice or give scores based on some criteria. Similarly, students can log in and retrieve the rubric advice left by the instructor. We mocked the behavior of the user (both as an instructor and student) to see how different scenarios work, like modifying, saving and retrieving advice and building feature tests for it. The testing frameworks used for the same were Selenium and Capybara.

== Test Plan ==

An instructor when creating a questionnaire, can associate marks with comments which can enable a student to understand what score is appropriate for a particular work.
An instructor can subsequently edit or delete an advice.
A student can view and use this rubric advice when peer reviewing other's work.
Thus the test cases formed check if an instructor is able to:

* Create a questionnaire
* Edit or delete an advice
Creating a rubric advice has not been added as a test case because both edit and delete advice make an instructor 'create' an advice. An additional test case to do the same would have slowed down the testing process and hence is not advisable.

'''Student Side:'''
A student, when filling a peer review should be able to see the rubric advice associated with a particular test score. We test this task through adding a test case in the peer_review_spec.rb since Peer Review is superset of the Rubric Advice feature as it is a task where a student uses the rubric advice and submit it.

Files changed: peer_review_spec.rb
The test case checks if student is able to select a rubric advice that the instructor has created and then submit it.
<pre>
it "able to view and use rubric advice", :js => true do
load_questionnaire
expect(page).to have_content "Show advice"
page.find('#showAdivce_1').click
expect(page).to have_content "5 - Good"
page.find("a", :text => "5 - Good").click
click_button "Save Review"
expect(page).to have_content "Your response was successfully saved."
end
</pre>

The existing code given creates the required environment for the test student. It sets up a team, assignment and other required elements for the test student to submit a review.
<pre>
before(:each) do
create(:assignment, name: "TestAssignment", directory_path: 'test_assignment')
create_list(:participant, 3)
create(:assignment_node)
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: 'review').first, due_at: Time.now.in_time_zone + 1.day)
create(:topic)
create(:topic, topic_name: "TestReview")
create(:team_user, user: User.where(role_id: 2).first)
create(:team_user, user: User.where(role_id: 2).second)
create(:assignment_team)
create(:team_user, user: User.where(role_id: 2).third, team: AssignmentTeam.second)
create(:signed_up_team)
create(:signed_up_team, team_id: 2, topic: SignUpTopic.second)
create(:assignment_questionnaire)
create(:question)
create(:question_advices)
end
</pre>

The rubric advice is prepared in factory.rb with the following code addition . This allows our test Student to get a ready rubric advice that he can choose.
<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

'''Instructor side:'''

Edit a certain review rubric, and add advice to it.
Test that when advice is added for a particular criterion, the advice can be retrieved and that it is exactly the advice that was added. Files added: review_rubric_spec.rb

<pre>
describe "Edit a rubric advice" do
it "is able to edit a review rubric advice" do
# creating a new rubric advice
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
# setting intital advice in the field
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# editing a review rubric - Setting any element with new data
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Edited the advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Edited the advice')
end
end

describe "Remove a rubric advice" do
it "should be able to delete a rubric advice" do
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# edit review advice to set to blank i.e. delete rubric advice
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
end
end
end
</pre>

Apart from the major test case for Rubric advice, it is essential to test if the logged in instructor is an authorized instructor. To test this, we have added the following test in review_rubric_spec.rb.
Also, the task of loading the questionnaire and the question types is implemented in separate methods to allow reuse.

<pre>

include InstructorInterfaceHelperSpec

# Feature test of rubric advice
describe "Edit rubric advice" do
before(:each) do
assignment_setup
end

# Login test
describe "Login as instructor" do
it "logs in with valid username and password" do
login_as("instructor6")
visit '/tree_display/list'
expect(page).to have_content("Manage content")
end

it "logs in with invalid username and password" do
visit root_path
fill_in 'login_name', with: 'instructor6'
fill_in 'login_password', with: 'wrongpassword'
click_button 'SIGN IN'
expect(page).to have_text('Your username or password is incorrect.')
end
end

def load_questionnaire
login_as("instructor6")
visit '/questionnaires/new?model=ReviewQuestionnaire&private=0'
fill_in('questionnaire_name', with: 'DummyReview')
fill_in('questionnaire_min_question_score', with: '0')
fill_in('questionnaire_max_question_score', with: '5')
select('no', from: 'questionnaire_private')
click_button "Create"
end

def load_question question_type
load_questionnaire
fill_in('question_total_num', with: '1')
select(question_type, from: 'question_type')
click_button "Add"
end
</pre>

'''Factories.rb'''

<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

It associates a merit score with each type of advice. As an example, 5 denotes 'very good'.

== Results ==

* [https://youtu.be/0a5FUXhJHBQ Demo Video of Testing]
* Build passing with Coverage increase of +0.3%

[[File:coverage.jpg]]

== Testing Instructions ==
* [https://github.com/expertiza/expertiza Clone Expertiza on local Repository]
* [http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation#Development_Environment_Setup_Guides Setup expertiza on your local machine]
* Run the test cases:
<pre>spec/features/peer_review_spec.rb </pre>
<pre>spec/features/review_rubric_spec.rb using [https://relishapp.com/rspec Rspec]</pre>

== References ==

* [https://github.com/rcoutin/expertiza Forked Github Expertiza Repository]
* [https://github.com/expertiza/expertiza Github Expertiza Repository]
* [https://relishapp.com/rspec Rspec Documentation]

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-11-03T03:56:59Z

Pjain15: /* Results */

== Introduction ==

Expertiza is a web application which provides a dashboard to the students where they can submit and peer-review assignments, projects, codes, and other such objects. It allows students to review each other’s work and improve their work upon this feedback. Rubric advice allows reviewers to see what characteristics of work merit a particular score.

== The problem statement ==

Rubric advice lets a user see what criterion or characteristics of work merit a particular score. An instructor can retrieve peer review assignments and leave some advice or give scores based on some criteria. Similarly, students can log in and retrieve the rubric advice left by the instructor. We mocked the behavior of the user (both as an instructor and student) to see how different scenarios work, like modifying, saving and retrieving advice and building feature tests for it. The testing frameworks used for the same were Selenium and Capybara.

== Test Plan ==

An instructor when creating a questionnaire, can associate marks with comments which can enable a student to understand what score is appropriate for a particular work.
An instructor can subsequently edit or delete an advice.
A student can view and use this rubric advice when peer reviewing other's work.
Thus the test cases formed check if an instructor is able to:
* correctly log in
* create a questionnaire
* edit or delete an advice

'''Student Side:'''
A student, when filling a peer review should be able to see the rubric advice associated with a particular test score. We test this task through adding a test case in the peer_review_spec.rb since Peer Review is superset of the Rubric Advice feature as it is a task where a student uses the rubric advice and submit it.

Files changed: peer_review_spec.rb
The test case checks if student is able to select a rubric advice that the instructor has created and then submit it.
<pre>
it "able to view and use rubric advice", :js => true do
load_questionnaire
expect(page).to have_content "Show advice"
page.find('#showAdivce_1').click
expect(page).to have_content "5 - Good"
page.find("a", :text => "5 - Good").click
click_button "Save Review"
expect(page).to have_content "Your response was successfully saved."
end
</pre>

The existing code given creates the required environment for the test student. It sets up a team, assignment and other required elements for the test student to submit a review.
<pre>
before(:each) do
create(:assignment, name: "TestAssignment", directory_path: 'test_assignment')
create_list(:participant, 3)
create(:assignment_node)
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: 'review').first, due_at: Time.now.in_time_zone + 1.day)
create(:topic)
create(:topic, topic_name: "TestReview")
create(:team_user, user: User.where(role_id: 2).first)
create(:team_user, user: User.where(role_id: 2).second)
create(:assignment_team)
create(:team_user, user: User.where(role_id: 2).third, team: AssignmentTeam.second)
create(:signed_up_team)
create(:signed_up_team, team_id: 2, topic: SignUpTopic.second)
create(:assignment_questionnaire)
create(:question)
create(:question_advices)
end
</pre>

The rubric advice is prepared in factory.rb with the following code addition . This allows our test Student to get a ready rubric advice that he can choose.
<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

'''Instructor side:'''

Edit a certain review rubric, and add advice to it.
Test that when advice is added for a particular criterion, the advice can be retrieved and that it is exactly the advice that was added. Files added: review_rubric_spec.rb

<pre>
describe "Edit a rubric advice" do
it "is able to edit a review rubric advice" do
# creating a new rubric advice
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
# setting intital advice in the field
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# editing a review rubric - Setting any element with new data
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Edited the advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Edited the advice')
end
end

describe "Remove a rubric advice" do
it "should be able to delete a rubric advice" do
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# edit review advice to set to blank i.e. delete rubric advice
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
end
end
end
</pre>

Apart from the major test case for Rubric advice, it is essential to test if the logged in instructor is an authorized instructor. To test this, we have added the following test in review_rubric_spec.rb.
Also, the task of loading the questionnaire and the question types is implemented in separate methods to allow reuse.

<pre>

include InstructorInterfaceHelperSpec

# Feature test of rubric advice
describe "Edit rubric advice" do
before(:each) do
assignment_setup
end

# Login test
describe "Login as instructor" do
it "logs in with valid username and password" do
login_as("instructor6")
visit '/tree_display/list'
expect(page).to have_content("Manage content")
end

it "logs in with invalid username and password" do
visit root_path
fill_in 'login_name', with: 'instructor6'
fill_in 'login_password', with: 'wrongpassword'
click_button 'SIGN IN'
expect(page).to have_text('Your username or password is incorrect.')
end
end

def load_questionnaire
login_as("instructor6")
visit '/questionnaires/new?model=ReviewQuestionnaire&private=0'
fill_in('questionnaire_name', with: 'DummyReview')
fill_in('questionnaire_min_question_score', with: '0')
fill_in('questionnaire_max_question_score', with: '5')
select('no', from: 'questionnaire_private')
click_button "Create"
end

def load_question question_type
load_questionnaire
fill_in('question_total_num', with: '1')
select(question_type, from: 'question_type')
click_button "Add"
end
</pre>

'''Factories.rb'''

<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

It associates a merit score with each type of advice. As an example, 5 denotes 'very good'.

== Results ==

* [https://youtu.be/0a5FUXhJHBQ Demo Video of Testing]
* Build passing with Coverage increase of +0.3%

[[File:coverage.jpg]]

== Testing Instructions ==
* [https://github.com/expertiza/expertiza Clone Expertiza on local Repository]
* [http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation#Development_Environment_Setup_Guides Setup expertiza on your local machine]
* Run the test cases:
<pre>spec/features/peer_review_spec.rb </pre>
<pre>spec/features/review_rubric_spec.rb using [https://relishapp.com/rspec Rspec]</pre>

== References ==

* [https://github.com/rcoutin/expertiza Forked Github Expertiza Repository]
* [https://github.com/expertiza/expertiza Github Expertiza Repository]
* [https://relishapp.com/rspec Rspec Documentation]

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-11-03T03:53:05Z

Pjain15: /* Results */

== Introduction ==

Expertiza is a web application which provides a dashboard to the students where they can submit and peer-review assignments, projects, codes, and other such objects. It allows students to review each other’s work and improve their work upon this feedback. Rubric advice allows reviewers to see what characteristics of work merit a particular score.

== The problem statement ==

Rubric advice lets a user see what criterion or characteristics of work merit a particular score. An instructor can retrieve peer review assignments and leave some advice or give scores based on some criteria. Similarly, students can log in and retrieve the rubric advice left by the instructor. We mocked the behavior of the user (both as an instructor and student) to see how different scenarios work, like modifying, saving and retrieving advice and building feature tests for it. The testing frameworks used for the same were Selenium and Capybara.

== Test Plan ==

An instructor when creating a questionnaire, can associate marks with comments which can enable a student to understand what score is appropriate for a particular work.
An instructor can subsequently edit or delete an advice.
A student can view and use this rubric advice when peer reviewing other's work.
Thus the test cases formed check if an instructor is able to:
* correctly log in
* create a questionnaire
* edit or delete an advice

'''Student Side:'''
A student, when filling a peer review should be able to see the rubric advice associated with a particular test score. We test this task through adding a test case in the peer_review_spec.rb since Peer Review is superset of the Rubric Advice feature as it is a task where a student uses the rubric advice and submit it.

Files changed: peer_review_spec.rb
The test case checks if student is able to select a rubric advice that the instructor has created and then submit it.
<pre>
it "able to view and use rubric advice", :js => true do
load_questionnaire
expect(page).to have_content "Show advice"
page.find('#showAdivce_1').click
expect(page).to have_content "5 - Good"
page.find("a", :text => "5 - Good").click
click_button "Save Review"
expect(page).to have_content "Your response was successfully saved."
end
</pre>

The existing code given creates the required environment for the test student. It sets up a team, assignment and other required elements for the test student to submit a review.
<pre>
before(:each) do
create(:assignment, name: "TestAssignment", directory_path: 'test_assignment')
create_list(:participant, 3)
create(:assignment_node)
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: 'review').first, due_at: Time.now.in_time_zone + 1.day)
create(:topic)
create(:topic, topic_name: "TestReview")
create(:team_user, user: User.where(role_id: 2).first)
create(:team_user, user: User.where(role_id: 2).second)
create(:assignment_team)
create(:team_user, user: User.where(role_id: 2).third, team: AssignmentTeam.second)
create(:signed_up_team)
create(:signed_up_team, team_id: 2, topic: SignUpTopic.second)
create(:assignment_questionnaire)
create(:question)
create(:question_advices)
end
</pre>

The rubric advice is prepared in factory.rb with the following code addition . This allows our test Student to get a ready rubric advice that he can choose.
<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

'''Instructor side:'''

Edit a certain review rubric, and add advice to it.
Test that when advice is added for a particular criterion, the advice can be retrieved and that it is exactly the advice that was added. Files added: review_rubric_spec.rb

<pre>
describe "Edit a rubric advice" do
it "is able to edit a review rubric advice" do
# creating a new rubric advice
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
# setting intital advice in the field
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# editing a review rubric - Setting any element with new data
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Edited the advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Edited the advice')
end
end

describe "Remove a rubric advice" do
it "should be able to delete a rubric advice" do
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# edit review advice to set to blank i.e. delete rubric advice
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
end
end
end
</pre>

Apart from the major test case for Rubric advice, it is essential to test if the logged in instructor is an authorized instructor. To test this, we have added the following test in review_rubric_spec.rb.
Also, the task of loading the questionnaire and the question types is implemented in separate methods to allow reuse.

<pre>

include InstructorInterfaceHelperSpec

# Feature test of rubric advice
describe "Edit rubric advice" do
before(:each) do
assignment_setup
end

# Login test
describe "Login as instructor" do
it "logs in with valid username and password" do
login_as("instructor6")
visit '/tree_display/list'
expect(page).to have_content("Manage content")
end

it "logs in with invalid username and password" do
visit root_path
fill_in 'login_name', with: 'instructor6'
fill_in 'login_password', with: 'wrongpassword'
click_button 'SIGN IN'
expect(page).to have_text('Your username or password is incorrect.')
end
end

def load_questionnaire
login_as("instructor6")
visit '/questionnaires/new?model=ReviewQuestionnaire&private=0'
fill_in('questionnaire_name', with: 'DummyReview')
fill_in('questionnaire_min_question_score', with: '0')
fill_in('questionnaire_max_question_score', with: '5')
select('no', from: 'questionnaire_private')
click_button "Create"
end

def load_question question_type
load_questionnaire
fill_in('question_total_num', with: '1')
select(question_type, from: 'question_type')
click_button "Add"
end
</pre>

'''Factories.rb'''

<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

It associates a merit score with each type of advice. As an example, 5 denotes 'very good'.

== Results ==

* [https://youtu.be/0a5FUXhJHBQ Demo Video of Testing]
* Build passed with Coverage increase of +0.3%

[[File:coverage.jpg]]

== Testing Instructions ==
* [https://github.com/expertiza/expertiza Clone Expertiza on local Repository]
* [http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation#Development_Environment_Setup_Guides Setup expertiza on your local machine]
* Run the test cases:
<pre>spec/features/peer_review_spec.rb </pre>
<pre>spec/features/review_rubric_spec.rb using [https://relishapp.com/rspec Rspec]</pre>

== References ==

* [https://github.com/rcoutin/expertiza Forked Github Expertiza Repository]
* [https://github.com/expertiza/expertiza Github Expertiza Repository]
* [https://relishapp.com/rspec Rspec Documentation]

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-10-29T16:41:40Z

Pjain15:

== Introduction ==

Expertiza is a web application which provides a dashboard to the students where they can submit and peer-review assignments, projects, codes, and other such objects. It allows students to review each other’s work and improve their work upon this feedback. Rubric advice allows reviewers to see what characteristics of work merit a particular score.

== The problem statement ==

Rubric advice lets a user see what criterion or characteristics of work merit a particular score. An instructor can retrieve peer review assignments and leave some advice or give scores based on some criteria. Similarly, students can log in and retrieve the rubric advice left by the instructor. We mocked the behavior of the user (both as an instructor and student) to see how different scenarios work, like modifying, saving and retrieving advice and building feature tests for it. The testing frameworks used for the same were Selenium and Capybara.

== Tasks identified ==

'''Student Side:'''
A student, when filling a peer review should be able to see the rubric advice associated with a particular test score. We test this task through adding a test case in the peer_review_spec.rb since Peer Review is superset of the Rubric Advice feature as it is a task where a student uses the rubric advice and submit it.

Files changed: peer_review_spec.rb
The test case checks if student is able to select a rubric advice that the instructor has created and then submit it.
<pre>
it "able to view and use rubric advice", :js => true do
load_questionnaire
expect(page).to have_content "Show advice"
page.find('#showAdivce_1').click
expect(page).to have_content "5 - Good"
page.find("a", :text => "5 - Good").click
click_button "Save Review"
expect(page).to have_content "Your response was successfully saved."
end
</pre>

The existing code given creates the required environment for the test student. It sets up a team, assignment and other required elements for the test student to submit a review.
<pre>
before(:each) do
create(:assignment, name: "TestAssignment", directory_path: 'test_assignment')
create_list(:participant, 3)
create(:assignment_node)
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: 'review').first, due_at: Time.now.in_time_zone + 1.day)
create(:topic)
create(:topic, topic_name: "TestReview")
create(:team_user, user: User.where(role_id: 2).first)
create(:team_user, user: User.where(role_id: 2).second)
create(:assignment_team)
create(:team_user, user: User.where(role_id: 2).third, team: AssignmentTeam.second)
create(:signed_up_team)
create(:signed_up_team, team_id: 2, topic: SignUpTopic.second)
create(:assignment_questionnaire)
create(:question)
create(:question_advices)
end
</pre>

The rubric advice is prepared in factory.rb with the following code addition . This allows our test Student to get a ready rubric advice that he can choose.
<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

'''Instructor side:'''

Edit a certain review rubric, and add advice to it.
Test that when advice is added for a particular criterion, the advice can be retrieved and that it is exactly the advice that was added. Files added: review_rubric_spec.rb

<pre>
describe "Edit a rubric advice" do
it "is able to edit a review rubric advice" do
# creating a new rubric advice
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
# setting intital advice in the field
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# editing a review rubric - Setting any element with new data
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Edited the advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Edited the advice')
end
end

describe "Remove a rubric advice" do
it "should be able to delete a rubric advice" do
load_question 'Criterion'
click_button "Edit/View advice"
expect(page).to have_content('Edit an existing questionnaire')
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Initial advice")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
expect(page).to have_content('Initial advice')
# edit review advice to set to blank i.e. delete rubric advice
first(:css, "textarea[id^='horizontal_'][id$='advice']").set("")
click_button "Save and redisplay advice"
expect(page).to have_content('advice was successfully saved')
end
end
end
</pre>

Apart from the major test case for Rubric advice, it is essential to test if the logged in instructor is an authorized instructor. To test this, we have added the following test in review_rubric_spec.rb.
Also, the task of loading the questionnaire and the question types is implemented in separate methods to allow reuse.

<pre>

include InstructorInterfaceHelperSpec

# Feature test of rubric advice
describe "Edit rubric advice" do
before(:each) do
assignment_setup
end

# Login test
describe "Login as instructor" do
it "logs in with valid username and password" do
login_as("instructor6")
visit '/tree_display/list'
expect(page).to have_content("Manage content")
end

it "logs in with invalid username and password" do
visit root_path
fill_in 'login_name', with: 'instructor6'
fill_in 'login_password', with: 'wrongpassword'
click_button 'SIGN IN'
expect(page).to have_text('Your username or password is incorrect.')
end
end

def load_questionnaire
login_as("instructor6")
visit '/questionnaires/new?model=ReviewQuestionnaire&private=0'
fill_in('questionnaire_name', with: 'DummyReview')
fill_in('questionnaire_min_question_score', with: '0')
fill_in('questionnaire_max_question_score', with: '5')
select('no', from: 'questionnaire_private')
click_button "Create"
end

def load_question question_type
load_questionnaire
fill_in('question_total_num', with: '1')
select(question_type, from: 'question_type')
click_button "Add"
end
</pre>

'''Factories.rb'''

<pre>
factory :question_advices, class: QuestionAdvice do
question_id 1
score 5
advice "Good work"
end
</pre>

It associates a merit score with each type of advice. As an example, 5 denotes 'very good'.

== Test Plan ==

An instructor when creating a questionnaire, can associate marks with comments which can enable a student to understand what score is appropriate for a particular work.

== Testing Instructions ==
* [https://github.com/expertiza/expertiza Clone Expertiza on local Repository]
* [http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation#Development_Environment_Setup_Guides Setup expertiza on your local machine]
* Run the test cases:
<pre>spec/features/peer_review_spec.rb </pre>
<pre>spec/features/review_rubric_spec.rb using [https://relishapp.com/rspec Rspec]</pre>

== References ==

* [https://github.com/rcoutin/expertiza Forked Github Expertiza Repository]
* [https://github.com/expertiza/expertiza Github Expertiza Repository]
* [https://relishapp.com/rspec Rspec Documentation]
* [https://youtu.be/wB9a--SMNVs Demo Video]

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-10-27T17:55:58Z

Pjain15:

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-10-27T17:28:02Z

Pjain15:

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-10-27T17:17:03Z

Pjain15:

CSC/ECE 517 Fall 2017/E1754 Feature test of rubric advice

2017-10-27T17:09:57Z

Pjain15:

CSC/ECE 517 Fall 2017/E1754 Feature test of Rubric Advice.rb

2017-10-26T21:39:21Z

Pjain15: Created page with "EXPERTIZA"

EXPERTIZA