MDL-61135 question: add behat test for tag filtering
This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
@core @core_question
|
||||
Feature: The questions in the question bank can be filtered by tags
|
||||
In order to find the questions I need
|
||||
As a teacher
|
||||
I want to filter the questions by tags
|
||||
|
||||
Background:
|
||||
Given the following "users" exist:
|
||||
| username | firstname | lastname | email |
|
||||
| teacher1 | Teacher | 1 | teacher1@example.com |
|
||||
And the following "courses" exist:
|
||||
| fullname | shortname | format |
|
||||
| Course 1 | C1 | weeks |
|
||||
And the following "course enrolments" exist:
|
||||
| user | course | role |
|
||||
| teacher1 | C1 | editingteacher |
|
||||
And the following "question categories" exist:
|
||||
| contextlevel | reference | name |
|
||||
| Course | C1 | Test questions |
|
||||
And the following "questions" exist:
|
||||
| questioncategory | qtype | name | user | questiontext |
|
||||
| Test questions | essay | question 1 name | admin | Question 1 text |
|
||||
| Test questions | essay | question 2 name | teacher1 | Question 2 text |
|
||||
And I log in as "teacher1"
|
||||
And I am on "Course 1" course homepage
|
||||
And I navigate to "Questions" node in "Course administration > Question bank"
|
||||
And I click on "Edit" "link" in the "question 1 name" "table_row"
|
||||
And I set the following fields to these values:
|
||||
| Tags | foo |
|
||||
And I press "id_submitbutton"
|
||||
And I click on "Edit" "link" in the "question 2 name" "table_row"
|
||||
And I set the following fields to these values:
|
||||
| Tags | bar |
|
||||
And I press "id_submitbutton"
|
||||
|
||||
@javascript
|
||||
Scenario: The questions can be filtered by tag
|
||||
When I set the field "Filter by tags..." to "foo"
|
||||
And I press key "13" in the field "Filter by tags..."
|
||||
Then I should see "question 1 name" in the "categoryquestions" "table"
|
||||
And I should not see "question 2 name" in the "categoryquestions" "table"
|
||||
Reference in New Issue
Block a user