Skip to content
Snippets Groups Projects
Select Git revision
  • f6cb8d92494c6bbf8d82af6158671fefeb16680b
  • master default protected
  • hsh_v3.11
  • hsh_v3.10-r6
  • hsh_v3.10-r3
  • v3.9-r9
  • v3.10-r6
  • v3.9-r8
  • v3.10-r5
  • v3.9-r7
  • v3.10-r4
  • v3.9-r6
  • v3.10-r3
  • v3.9-r5
  • v3.10-r2
  • v3.9-r4
  • v3.10-r1
  • v3.9-r3
  • v3.9-r2
  • v3.9-r1
  • v3.8-r5
  • v3.8-r4
  • v3.8-r3
  • v3.8-r2
  • v3.8-r1
25 results

theme_boost_campus_advanced_settings.feature

Blame
  • user avatar
    Kathrin Osswald authored
    f6cb8d92
    History
    theme_boost_campus_advanced_settings.feature 2.99 KiB
    @theme @theme_boost_campus @theme_boost_campus_advanced_settings
    Feature: Configuring the theme_boost_campus plugin for the "Advanced settings" tab
      In order to use the features
      As admin
      I need to be able to configure the theme Boost Campus plugin
    
      Background:
        Given the following "users" exist:
          | username |
          | student1 |
          | teacher1 |
        And the following "courses" exist:
          | fullname | shortname |
          | Course 1 | C1        |
        And the following "course enrolments" exist:
          | user     | course | role           |
          | teacher1 | C1     | editingteacher |
          | student1 | C1     | student        |
        # There is a nasty bug with Behat-testing this theme that the footer is not displayed until the settings
        # of the theme are stored manually. It seems not to be sufficient to just rely on the default settings being
        # stored during the installation of the theme. Until we find the root of this bug, we circumvent it by setting the
        # brand color manually and within this process making sure that all settings are really stored to the database.
        And I log in as "admin"
        And I navigate to "Appearance > Boost Campus" in site administration
        And I click on "General settings" "link"
        And I set the field "id_s_theme_boost_campus_brandcolor" to "#7a99ac"
        And I press "Save changes"
        And I log out
    
      # This is derivated from theme Boost and should be covered there with tests
      # Scenario: Add "Raw initial SCSS"
    
      # This is derivated from theme Boost and should be covered there with tests
      # Scenario: Add "Raw SCSS"
    
      # This is not testable with Behat
      # Scenario: "Catch keyboard commands"
    
      Scenario: Set "Position of "Add a block" widget" to "At the bottom of the default block region"
        Given the following config values are set as admin:
          | config            | value                 | plugin             |
          | addablockposition | positionblockregion   | theme_boost_campus |
        And I log in as "admin"
        And I navigate to "Development > Purge caches" in site administration
        And I press "Purge all caches"
        And I log out
        When I log in as "teacher1"
        And I am on "Course 1" course homepage with editing mode on
        Then I should see "Add a block" in the "#block-region-side-pre" "css_element"
        And I should not see "Add a block" in the "#nav-drawer" "css_element"
    
      Scenario: Set "Position of "Add a block" widget" to "At the bottom of the nav drawer"
        Given the following config values are set as admin:
          | config            | value                 | plugin             |
          | addablockposition | positionnavdrawer   | theme_boost_campus |
        And I log in as "admin"
        And I navigate to "Development > Purge caches" in site administration
        And I press "Purge all caches"
        And I log out
        When I log in as "teacher1"
        And I am on "Course 1" course homepage with editing mode on
        Then I should see "Add a block" in the "#nav-drawer" "css_element"
        And "#block-region-side-pre" "css_element" should not exist