Skip to content

Latest commit

 

History

History
34 lines (21 loc) · 1.86 KB

RunningLinkyClicky.md

File metadata and controls

34 lines (21 loc) · 1.86 KB
Raw

Running Linky Clicky:

Running the tests in Link Clicky involves pulling together a Behat command with the appropriate options and path. Refer to [Using Linky Clicky] (https://github.com/SU-SWS/linky_clicky/blob/5.x/UsingLinkyClicky.md) to learn how the options are implemented for Linky Clicky. To get a list describing all the options for Behat tests enter: $ ../../bin/behat --help

To execute the tests for a product/site/environment/etc:

  1. Start up Selenium

  2. Verify your drush aliases. The aliases are usually defined in your ~/.drush directory.

  3. Navigate to the product/site/environment/ directory. For this example we'll run tests for sites running the JSE product, and the current working directory will be: linky_clicky/products/jse

  4. Define the site profile in the behat.local.yml. You will need a behat.local.yml file in each test directory. For this example, the profile will be: local-jse-dev

  5. Use the version of Behat included with the repository. Because the tests in this directory use this version of Behat, and this version of Behat may include patches, you'll want to use it for running these tests. To access the Behat executable from the JSE product directory, at the command prompt you'll use ../../bin/behat

  6. Build your Behat command for running your tests. In [Using Linky Clicky] (https://github.com/SU-SWS/linky_clicky/blob/5.x/UsingLinkyClicky.md) we describe how many Behat options will be used. When testing, you'll need to identify and use the appropriate options.
    For our purposes we'll use the following options: profile (-p), suite (-s), and path, and the resulting command is this:

$ ../../bin/behat -p local-jse-dev -s live features

See [README] (https://github.com/SU-SWS/linky_clicky/blob/5.x/README.md)

See [Using Linky Clicky] (https://github.com/SU-SWS/linky_clicky/blob/5.x/UsingLinkyClicky.md)