• Development

    Combining Steps in Behat for Drupal

    / January 22, 2019

    Lately I have found myself repeating several lines of behat steps over and over again. Here is a sample of the behat code I use to choose a specific checkbox from an entity browser popup:

    There are a few steps in here that are custom, but explaining them would be beyond the scope of this post; just assume they do what they describe (switching focus to an iframe, and clicking a checkbox).

    The issue I was having is that every time I wanted to do that one action (pick an image from an entity browser) I was repeating all 8 lines of code.

    I began looking for ways of making this set of steps repeatable. After some failed attempts at extending MinkContext and MinkAwareContext I came across scenario hooks via this StackOverflow post. I discovered the @BeforeScenario, which is executed before every scenario in each feature (where it’s used). Using this hook to access contexts from other contexts was documented on behat.org but required a few tweaks for the Drupal implementation. Here is what I ended up doing (based on the default FeatureContext.php you get when you install behat for the project:

    read more
  • Development

    Adding Level Number Class to Menu Items in Drupal 8

    / January 15, 2019

    This is a quick post showing how to add level classes to menu items in Drupal 8.

    Here’s the result, showing the additional menu--level-N  and menu-item--level-N  classes:

    Result

    Step 1: Create a New Twig template File

    Determine which Twig template you need to override. I recommend reading the official docs on this. In my case, for a menu called infofor, I copied docroot/core/themes/classy/templates/navigation/menu.html.twig to docroot/themes/custom/mytheme/templates/navigation/menu--infofor.html.twig .

    Step 2: Update the Twig Code

    read more
  • Development

    Setting Drupal 8 Node Properties with Behat

    / January 12, 2019

    The title of this post could also have been “Opening and Closing a Details Element with Behat” or “Clicking Any Element with Behat”.

    The Drupal 8 node add/edit screen has a number properties on the right side of the screen. I wanted to use Behat to click the “Provide a menu link” checkbox. On page load this MENU SETTINGS pane is closed like the others.

    Here’s an example:

    Node add/edit

    The “URL SETTINGS”, “MENU SETTINGS”, actually mask a <details>  element.

    The “MENU SETTINGS” markup looks like this:

    Menu settings markup

    I expected to be able to write a few lines of Behat like this:

    Unfortunately this results in the failure: element not interactable.

    So, I thought I may need to first click to open the MENU SETTINGS pane so that I can see the checkbox before I try to click it. I modified my code to look like this:

    Unfortunately this results in the failure: Link with id|title|alt|text “Menu settings” not found.

    I tried using the edit-menu  id, “MENU SETTINGS” in all caps, etc. but it always resulted in the same “Link with …”

    I realized the click step is only looking for links.

    Solution

    I added a new step definition to my features/bootstrap/FeatureContext.php file:

    I updated my Behat code and found success!
    read more