CSC/ECE 517 Fall 2015 E1582 Create integration tests for the instructor interface using capybara and rspec: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 9: Line 9:
** 2 rounds of review
** 2 rounds of review
** Has no topics / has topics
** Has no topics / has topics
** Staggered-deadline assignments
** Staggered-deadline assignments (UPDATE: As indicated by Zhewei Hu, this feature has bugs, so we didn't implemented the test for this)
 


== '''Background''' ==
== '''Background''' ==
Line 94: Line 93:
# Choose a certain reviewer, click "reviewer summary" button
# Choose a certain reviewer, click "reviewer summary" button
In the view review score page, review scores are expected to be shown.
In the view review score page, review scores are expected to be shown.


=== View author-feedback scores ===
=== View author-feedback scores ===
Line 105: Line 103:


=== Create a Two-round Review Assignment ===  
=== Create a Two-round Review Assignment ===  
Ensure to create an assignment which has two rounds of review, has a topic or does not has a topic, and has a staggered-deadline.
Ensure to create an assignment which has two rounds of review, has a topic or does not has a topic. As indicated by Zhewei Hu, the staggered deadline feature contains bugs. So we didn't test this feature in the integration tests.
 
We implemented these two tests using selenium-webdriver as they involve the interaction with the Javascript components. However, a side effect is any change to the database will be recorded. To clean up the database, we visit the Assignments page again after tests and delete the assignments added in the tests.


*Scenario 1: The assignment does not have a topic.  
*Scenario 1: The assignment does not have a topic.  
Line 113: Line 113:
# Fill in the “Assignment Name” as “test_6”
# Fill in the “Assignment Name” as “test_6”
# Fill in the “Submission directory” as “test_6”
# Fill in the “Submission directory” as “test_6”
# Check “staggered deadline assignment”
# In the “Course” drop-down list, select as “CSC/ECE517 Spring 2015”
# In the “Course” drop-down list, select as “CSC/ECE517 Spring 2015”
# Chick the “rubrics” tab
# Click “create”
# In the “Review” drop-down list, choose “Chapter Review”
# In the “Author Feedback” drop-down list, choose “Author feedback OTD1”
# Click “Save”
# Click the “Due dates” tab
# Click the “Due dates” tab
# Fill in the “Number of review rounds” as 2
# Fill in the “Number of review rounds” as 2
# Click “Set”
# Click “Set”
# Click “Save”
# Click the “Due dates” tab
# Fill in the deadlines
# Click “Save”
# We expect the flash message “Assignment was successfully saved” would appear on the page.  
# We expect the flash message “Assignment was successfully saved” would appear on the page.  
# Click the “Assignments” tab
# Delete the assignment added in the test


*Scenario 2: The assignment has a topic.  
*Scenario 2: The assignment has a topic.  
Line 130: Line 132:
# Fill in the “Assignment Name” as “test_6”
# Fill in the “Assignment Name” as “test_6”
# Fill in the “Submission directory” as “test_6”
# Fill in the “Submission directory” as “test_6”
# Check “staggered deadline assignment”
# In the “Course” drop-down list, select as “CSC/ECE517 Spring 2015”
# In the “Course” drop-down list, select as “CSC/ECE517 Spring 2015”
# Click “create”
# Click the “Topics” tab
# Click the “Topics” tab
# Click the “New topic” button
# Click the “New topic” button
# Fill in the “Topic id”, “Topic name”, “Topic category”
# Fill in the “Topic id”, “Topic name”, “Topic category”
# Fill in the “Number of slots” as 5
# Fill in the “Number of slots” as 3
# Click “create”
# Click “create”
# Chick the “rubrics” tab
# In the “Review” drop-down list, choose “Chapter Review”
# In the “Author Feedback” drop-down list, choose “Author feedback OTD1”
# Click the “Due dates” tab
# Click the “Due dates” tab
# Fill in the “Number of review rounds” as 2
# Fill in the “Number of review rounds” as 2
# Click “Set”
# Click “Set”
# Click “Save”
# Click the “Due dates” tab
# Fill in the deadlines
# Click “Save”
# Click “Save”
# We expect the flash message “Assignment was successfully saved” would appear on the page.
# We expect the flash message “Assignment was successfully saved” would appear on the page.
# Click the “Assignments” tab
# Delete the assignment added in the test


=Execution=
=Execution=
Three methods were defined to make code DRY: <code>set_due_dates</code>, <code>create_assignment</code>, <code>login_with</code>.
The tests were executed by <code>rspec -fd</code> command from the terminal.
 
[[File:s1.png]]


[[File:method.png]]
[[File:s2.png]]


=Links=
=Links=
*Github repository: https://github.com/Hongyi23/expertiza/blob/fall2015/spec/features/instructor_interface_spec.rb
*Github repository: https://github.com/Hongyi23/expertiza/blob/fall2015/spec/features/instructor_interface_spec.rb
*Demo vedios: https://www.youtube.com/watch?v=B--Zn1QOgUA&feature=youtu.be
=References=
=References=
<references></references>
<references></references>

Latest revision as of 04:53, 5 December 2015

Purpose

This project is to create integration tests for the instructor interface of Expertiza. The UI procedures need to be tested are:

  • Log in
  • Create a course
  • View scores for an assignment
  • View review scores (“review report”)
  • View author-feedback scores
  • Create an assignment
    • 2 rounds of review
    • Has no topics / has topics
    • Staggered-deadline assignments (UPDATE: As indicated by Zhewei Hu, this feature has bugs, so we didn't implemented the test for this)

Background

RSpec

Rspec <ref>RSpec Wiki Page</ref> is a Behavior Driven Development (BDD) framework for Ruby. It is composed of 4 main parts <ref>RSpec Official Website</ref>:

rspec-core
The spec runner, providing a rich command line program, flexible and customizable reporting, and an API to organize your code examples.

An example of running rspec file in terminal: rspec spec/model_spec.rb

rspec-expectations
Provides a readable API to express expected outcomes of a code example.
rspec-mocks
Test double framework, providing multiple types of fake objects to allow you to tightly control the environment in which your specs run.
rspec-rails
Supports using RSpec to test Ruby on Rails applications in place of Rails' built-in test framework.

Capybara

Capybara is a web-based automation test tool that simulates a real user to follow the scenarios of user stories.<ref>Capybara on GitHub</ref> It could interact with app to receive pages, parse the HTML and submit forms as a user would.<ref>Introducing cucumber & capybara on YouTube</ref> Used with RSpec and Ruby on Rails (version 1.9 or later), capybara makes it easier to write integration tests. <ref>Using Capybara in Rails 3</ref> It is used on the top of an underlying web-based driver and offers a user-friendly DSL (Domain Specific Language) to describe actions executed by the underlying web driver. Such as rack::test, selenium-webdriver and capybara-webkit.<ref>The Basics of Capybara and Improving Your Tests</ref>

In this project, we use capybara with rspec by adding the following line: require 'capybara/rspec' Then put capybara specs in spec/features.

Integration test

Integration test is a software testing definition that we combine modules then test them as one group. It is an important application testing way. It is always adapted after unit testing, we need to combine different units to test the functionalities and verify that the aggregated group could deliver its output properly. The purpose of integration test is to verify the functionality of interface between interacted parts, also we can know performance of the subsystems. The integration testing has two types, big bang top down and bottom up.

  • Big Bang

In this type, since all the application is combined with all major usage modules. So we test them under usage model testing, which means we can simulate the users' acts under testing environment. When doing this, we can test if all the expected components is got when we actually do the same way under production environment. It is an effective way to test the functionalities and got better coverage since we are creating the realistic scenarios. It will make sure the application can have proper output when a user does the same input.

  • Top down and Bottom up

Top down and bottom up is another type of integration testing. For top down, we test the top integrated module firstly and test the ranch of it again and again, then we can test all the related modules finally. For Bottom up way, we test the most basic module at first and check the module that containing this basic module. The advantage of it is that we can find the bug easier because we will not miss any branch that we use. However, it is time consuming in this way.<ref>Integration testing on Wikipedia</ref>


Test Plan

Based on the project requirements, the testing can be divided into the following 6 features:

  1. Log in: ensure an instructor is able to login to the system.
  2. Create a course: ensure an instructor is able to create a course.
  3. View scores for an assignment: ensure that the score of a certain assignment can be viewed.
  4. View review scores (“review report”): ensure to view the score of a review.
  5. View author-feedback scores: ensure to view the score of an author feedback.
  6. Create an assignment: ensure to create an assignment which has two rounds of review, has a topic or does not has a topic, and has a staggered-deadline.

Log in

  • Scenario 1: Login with valid username and password
  1. Log in as user: instructor6, password: password
  2. We expect the new page would be “tree_display/list”
  • Scenario 2: Login with invalid username and password
  1. Log in as user: instructor6, password: drowssap
  2. We expect the new page would be “password_retrieval/forgotten”

Create a course

  • Scenario 1: create a public course
  1. Sign in
  2. Click "Courses" to browse the course list
  3. Click "New public course" to create a public course
  4. Fill in the text area, and click "Create" button

After returning to the course list, the new course we created is expected to be shown.

  • Scenario 2: create a private course
  1. Sign in
  2. Click "Courses" to browse the course list
  3. Click "New private course" to create a private course
  4. Fill in the text area, and click "Create" button

After returning to the course list, the new course we created is expected to be shown.

View scores for an assignment

  1. sign in
  2. click "Assignments" to browse assignment list
  3. choose a certain assignment, click "View scores" button

In the grades review page, scores are expected to be shown.

View review scores (“review report”)

  1. Sign in
  2. Click "Assignments" to browse assignment list
  3. Choose a certain assignment, click "View review report" button

In the response report page, review report is expected to be shown.

  1. Choose a certain reviewer, click "reviewer summary" button

In the view review score page, review scores are expected to be shown.

View author-feedback scores

  1. Sign in
  2. Click "Assignments" to browse assignment list
  3. Choose a certain assignment, click "View scores" button
  4. Click "Show all teams" button
  5. Choose a certain contributor, click "show author feedbacks" button

In the grades review page, feedback scores from author are expected to be shown.

Create a Two-round Review Assignment

Ensure to create an assignment which has two rounds of review, has a topic or does not has a topic. As indicated by Zhewei Hu, the staggered deadline feature contains bugs. So we didn't test this feature in the integration tests.

We implemented these two tests using selenium-webdriver as they involve the interaction with the Javascript components. However, a side effect is any change to the database will be recorded. To clean up the database, we visit the Assignments page again after tests and delete the assignments added in the tests.

  • Scenario 1: The assignment does not have a topic.
  1. Log in as user: “instructor6”, password: “password”
  2. Click the “Assignments” tab
  3. Click the “New Public Assignment” button
  4. Fill in the “Assignment Name” as “test_6”
  5. Fill in the “Submission directory” as “test_6”
  6. In the “Course” drop-down list, select as “CSC/ECE517 Spring 2015”
  7. Click “create”
  8. Click the “Due dates” tab
  9. Fill in the “Number of review rounds” as 2
  10. Click “Set”
  11. Click “Save”
  12. Click the “Due dates” tab
  13. Fill in the deadlines
  14. Click “Save”
  15. We expect the flash message “Assignment was successfully saved” would appear on the page.
  16. Click the “Assignments” tab
  17. Delete the assignment added in the test
  • Scenario 2: The assignment has a topic.
  1. Log in as user: “instructor6”, password: “password”
  2. Click the “Assignments” tab
  3. Click the “New Public Assignment” button
  4. Fill in the “Assignment Name” as “test_6”
  5. Fill in the “Submission directory” as “test_6”
  6. In the “Course” drop-down list, select as “CSC/ECE517 Spring 2015”
  7. Click “create”
  8. Click the “Topics” tab
  9. Click the “New topic” button
  10. Fill in the “Topic id”, “Topic name”, “Topic category”
  11. Fill in the “Number of slots” as 3
  12. Click “create”
  13. Click the “Due dates” tab
  14. Fill in the “Number of review rounds” as 2
  15. Click “Set”
  16. Click “Save”
  17. Click the “Due dates” tab
  18. Fill in the deadlines
  19. Click “Save”
  20. We expect the flash message “Assignment was successfully saved” would appear on the page.
  21. Click the “Assignments” tab
  22. Delete the assignment added in the test

Execution

The tests were executed by rspec -fd command from the terminal.

Links

References

<references></references>

Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1582_Create_integration_tests_for_the_instructor_interface_using_capybara_and_rspec&oldid=100336"