Behat (software)

The topic of this article may not meet Wikipedia's notability guidelines for products and services. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources: "Behat" software – news · newspapers · books · scholar · JSTOR (July 2014) (Learn how and when to remove this message)

Behat
Developer	Konstantin Kudryashov
Initial release	8 September 2010; 15 years ago (2010-09-08)[1]
Stable release	3.27.0 / 23 November 2025; 21 days ago (2025-11-23)[1]
Repository	github.com/Behat/Behat
Written in	PHP
Operating system	Cross-platform
Type	Behavior-driven development
License	MIT License
Website	behat.org

Behat is a test framework for behavior-driven development written in the PHP programming language. Behat was created by Konstantin Kudryashov and its development is hosted on GitHub.

Behat is intended to aid communication between developers, clients and other stakeholders during a software development process. It allows the clear documentation of testable examples of the software's intended behaviour. Behat test scenarios are written with Gherkin,^[2] a business-readable domain-specific language following defined patterns.

Tests can be run at any point new code is introduced into a codebase to confirm no regressions within the existing test coverage are introduced. It can be used to directly test php code and is often used with Selenium to remote control browsers as part of the scenarios. The browsers under remote control can take videos^[3] or screenshots of failures. Using selenium or tools like selenoid^[4] a "grid" of browsers can be remote controlled for parallel test execution. There is also a module for running php only scenarios.^[5]

Like other BDD frameworks, Behat scenarios are a series of Given, When, and Then steps that explain a business case. The definition of these steps exist within method annotations of a class that extends the BehatContext.^[6]

Behat can output test results in a number of different formats, including JUnit XML and HTML^[7]

The preconditions after "Given" correspond to the PHP method name to execute:

Feature: Simple description of this feature’s story

  Describe benefit, role and feature or user story
  Use as many lines as needed

  Background:
    Given some step run for all scenarios
    
  Scenario: Scenario or example description
    Given I setup preconditions with:
      | data column 1 | data column 2 |
      | alice         | bob           |
    When I press the "blue" button
    Then the result is:
    """
    A multiple line
    string of data
    """

    #comments can be added as needed

  Scenario Outline: Scenario or example description using setting <setting>
    Given I setup config with "<setting>"
    When I push button "<button>"
    Then "<result>" happens
    Examples:
      | setting | button | result           |
      | a       | red    | there is a beep  |
      | b       | blue   | there is no beep |

• Official website

This computer-programming-related article is a stub. You can help Wikipedia by expanding it.

• v
• t
• e