diff --git a/tests/behat/default_settings.feature b/tests/behat/default_settings.feature index 1ed5123..d4c98dd 100644 --- a/tests/behat/default_settings.feature +++ b/tests/behat/default_settings.feature @@ -11,7 +11,6 @@ Feature: Change the default settings Given the authentication plugin "outage" is enabled And I am an administrator - Scenario Outline: Check if I can save the default settings. When I navigate to "Settings" node in "Site administration > Plugins > Authentication > Outage manager" And I set the following fields to these values: diff --git a/tests/behat/ipblock.feature b/tests/behat/ipblock.feature index 77e8566..c17d864 100644 --- a/tests/behat/ipblock.feature +++ b/tests/behat/ipblock.feature @@ -8,11 +8,9 @@ Feature: IP Blocker - An ongoing outage does not block Moodle execution, although it can trigger maintenance mode. - Maintenance mode completely blocks Moodle and can only be deactivated using the CLI. - Background: Given the authentication plugin "outage" is enabled - Scenario: Default IP Whitelist Settings Given I am an administrator And I am on homepage diff --git a/tests/behat/manage_outages.feature b/tests/behat/manage_outages.feature index 468cf99..3ade449 100644 --- a/tests/behat/manage_outages.feature +++ b/tests/behat/manage_outages.feature @@ -11,7 +11,6 @@ Feature: Manage outages - finished is an outage that has explicitly been marked as finished. - stopped is an outage that has already ended but not explicitly marked as finished. - Background: Always login as admin, enable the auth_outage plugin and go to the outage management page. Given the authentication plugin "outage" is enabled And I log in as "admin" @@ -26,7 +25,6 @@ Feature: Manage outages And I should see "Outage history" And I should see "No outages found." in the "#section_outage_history" "css_element" - Scenario Outline: Planned outages should include all outages not finished or stopped. Given there is a "" outage When I am on Outage Management Page @@ -40,7 +38,6 @@ Feature: Manage outages | finished | outage_history | | stopped | outage_history | - Scenario Outline: Planned and history outages have different actions. Given there is a "" outage When I am on Outage Management Page @@ -59,7 +56,6 @@ Feature: Manage outages | finished | see | see | not see | not see | not see | | stopped | see | see | not see | not see | not see | - Scenario: Create an outage using defaults. Given I am on Outage Management Page When I press "Create outage" @@ -67,7 +63,6 @@ Feature: Manage outages And I should not see "No outages found." in the "#section_planned_outages" "css_element" And I should see "No outages found." in the "#section_outage_history" "css_element" - Scenario: View an outage which should open in a new window or tab. Given there is a "waiting" outage And I am on Outage Management Page @@ -75,7 +70,6 @@ Feature: Manage outages Then I should be in a new window And I should see "Example of waiting outage" - Scenario: Clone an outage. Given there is a "waiting" outage And I am on Outage Management Page @@ -86,7 +80,6 @@ Feature: Manage outages Then I should see "Example of waiting outage" And I should see "My cloned outage" - Scenario: Edit an outage. Given there is a "warning" outage And I am on Outage Management Page @@ -98,7 +91,6 @@ Feature: Manage outages Then I should not see "Example of warning outage" And I should see "My previous warning outage" - Scenario: Delete an outage Given there is a "warning" outage And I am on Outage Management Page @@ -109,7 +101,6 @@ Feature: Manage outages Then I press "Delete" And I should not see "Example of warning outage" - Scenario: Finish an outage Given there is a "ongoing" outage And I am on Outage Management Page diff --git a/tests/behat/warningbar.feature b/tests/behat/warningbar.feature index e27f7f8..d769472 100644 --- a/tests/behat/warningbar.feature +++ b/tests/behat/warningbar.feature @@ -10,12 +10,10 @@ Feature: Warning bar - ongoing is an outage that has started, but not yet reached the stop time nor is marked as finished. - finished is an outage that has explicitly been marked as finished. - stopped is an outage that has already ended but not explicitly marked as finished. - - + Background: Given the authentication plugin "outage" is enabled - Scenario: This is how an outage should happend without maintenance mode and manual finish. Given there is the following outage: | warnbefore | startsin | stopsafter |