Behatch contexts provide most common behat tests.

This extension requires:

• Behat 2.4+
• Mink 1.4+
• Mink extension

Download the .phar archives:

• behat.phar - Behat itself
• mink.phar - Mink framework
• behatch_contexts.phar - Behatch contexts

And activate it in your in your behat.yml:

# behat.yml
default:
    # ...
    extensions:
        behatch_contexts.phar: ~

The easiest way to keep your suite updated is to use Composer.

You can add behatch contexts as dependancies for your project or rapidly bootstrap a behatch projects.

1. Define dependencies in your composer.json:

{
    "require": {
        ...

        "sanpi/behatch-contexts": "*"
    }
}

2. Install/update your vendors:

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

3. Activate extension by specifying its class in your behat.yml:

# behat.yml
default:
    # ...
    extensions:
        Sanpi\Behatch\Extension: ~

1. Download the behatch skeleton with composer:

$ curl http://getcomposer.org/installer | php
$ php composer.phar create-project sanpi/behatch-skeleton

In your main context, using behatch contexts:

<?php

use Behat\Behat\Context\BehatContext;
use Sanpi\Behatch\Context\BehatchContext;

class FeatureContext extends BehatContext
{
    public function __construct(array $parameters)
    {
        $this->useContext('behatch', new BehatchContext($parameters));
    }
}

After this, you wouldn't have new available step. You should enable, in behat.yml, the desired steps group:

Sanpi\Behatch\Extension:
    contexts:
        browser: ~
        debug: ~
        system: ~
        json: ~
        table: ~
        rest: ~
        xml: ~

• browser - more browser related steps (like mink)

• debug - helper steps for debuging

  • screenshot_dir - the directory where store screenshots
  • screen_id - then xorg screen id

• system - shell related steps

  • root - the root directory of the filesystem

• json - JSON related steps

  • evaluation_mode - javascript "foo.bar" or php "foo->bar"

• table - play with HTML the tables
• rest - send GET, POST, … requests and test the HTTP headers
• xml - XML related steps