shvetsgroup/parallelrunner

Parallel runner extension for Behat

v3.0.0 2018-06-20 14:10 UTC

Requires

• php: >=5.3.6
• ext-pcntl: *
• behat/behat: >3.0
• symfony/process: >=2.2.0

MIT

• Alexander Shvets

• BDD
• Behat
• runner
• parallel

README

Installation

This extension requires:

• Behat 2.4+

Through Composer

1. Set dependencies in your composer.json:

{
    "require": {
        ...
        "shvetsgroup/parallelrunner": "dev-master"
    }
}

1. Install/update your vendors:

$ curl http://getcomposer.org/installer | php
$ php composer.phar install

Configuration

As a bare minimum requirement, activate extension in your behat.yml:

default:
  extensions:
    shvetsgroup\ParallelRunner\Extension: ~

Separate environments for test processes

In certain cases, it's useful to run testing processes in separate environments (e.g. if test results of one test could break other test's data). For this purpose, you should define behat profiles in your configuration file and pass their names to "profile" parameter of the extension like this:

default:
  extensions:
    shvetsgroup\ParallelRunner\Extension:
      profiles:
        - environment1
        - environment2
...

environment1:
  some_data: ...

environment2:
  some_data: ...

Now, let's say you've run the test with 4 parallel processes. The first process will be launched with "environment1" profile, second with "environment2", and the rest with the default profile (or profile, which was passed in --config option).

Running tests in parallel by default

If you want all of your tests to run in parallel, just specify default number of parallel processes in your configuration file. Note: this number can be overridden by --parallel option.

default:
  extensions:
    shvetsgroup\ParallelRunner\Extension:
      process_count: 4

Usage

Use "--parallel" or "-l" parameter to specify number of concurrent test processes. For example:

$ bin/behat -l 4

Troubleshooting

1. If you're using Selenium, make sure it's launched in Hub mode to get all the benefits of parallelism (http://docs.seleniumhq.org/docs/07_selenium_grid.jsp).

2. This extension does not work with features which have closures as definitions (you'll get "Serialization of 'Closure' is not allowed" errors most likely).