Fork note

This is a fork of https://github.com/rkeet/behatch-contexts, which in turn is a fork of https://github.com/Behatch/contexts.

https://github.com/Behatch/contexts is abandoned and archived. Rkeet's fork above fixed a number of issues regarding PHP 8 compatibility:

• Reflection does not have a getClass function anymore
• PHP8 in combination with symfony/property-access 5.3 means there's no more leniency about accessing elements in an array as an object, and viceversa. It now only works with objects. Fix for that.

We're forking here for two reasons: first, Rkeet's fork could disappear at any point as it seemingly is for his own use. Second, we needed to tag 4.1 as master (but not 4.0) contained the fixes for correctly working with symfony/property-access.

Behatch contexts

Behatch contexts provide most common Behat tests.

Installation

This extension requires:

• Behat 3+
• Mink
• Mink extension

Project dependency

1. Install Composer
2. Require the package with Composer:

$ composer require --dev behatch/contexts

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

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

Project bootstraping

1. Download the Behatch skeleton with composer:

$ php composer.phar create-project behatch/skeleton

Browser, json, table and rest step need a mink configuration, see Mink extension for more information.

Usage

In behat.yml, enable desired contexts:

default:
    suites:
        default:
            contexts:
                - behatch:context:browser
                - behatch:context:debug
                - behatch:context:system
                - behatch:context:json
                - behatch:context:table
                - behatch:context:rest
                - behatch:context:xml

Examples

This project is self-tested, you can explore the features directory to find some examples.

Configuration

• browser - more browser related steps (like mink)
  • timeout - default timeout
• debug - helper steps for debugging
  • screenshotDir - the directory where store screenshots
• system - shell related steps
  • root - the root directory of the filesystem
• json - JSON related steps
  • evaluationMode - 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

Configuration Example

For example, if you want to change default directory to screenshots - you can do it this way:

default:
    suites:
        default:
            contexts:
                - behatch:context:debug:
                    screenshotDir: "var"

Translation