behat change_account_settings.feature doesn't test functionality
Bug #1703751 reported by
Rebecca Blundell
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This test is currently not testing actual functionality. It should be changed to check notification options are available and to check one or two actually work.
Changed in mahara: | |
status: | New → In Progress |
Changed in mahara: | |
importance: | Undecided → Medium |
milestone: | none → 17.10.0 |
Changed in mahara: | |
milestone: | 17.10.0 → 18.04.0 |
Changed in mahara: | |
status: | In Progress → Fix Committed |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Actually, we already have some tests to check what options are available - We can combine those with this: features/ settings/ notification_ choices. feature
test/behat/
This systematically tests all options are available for user and admin.
- Change feature text to accurately describe what the test does.
test/behat/ features/ settings/ notification_ setting_ order.feature choices. feature. setting_ order.feature
- take out all the "I should see" steps as if they aren't on the page, the "should appear" steps won't work anyway.
- Add the remaining steps as a Scenario called "Check options are in alphabetical order" to notification_
- Delete notification_
- At the end of the main scenario of notification_ choices. feature, after the I press "Save" step, add the steps: account_ settings. feature choices. feature as notification_ settings. feature
And I should see "Preferences saved"
And I should not see "Delete account"
- Delete the change_
- Rename notification_