JBehave is a framework for Behaviour-Driven Development (BDD). BDD is an evolution of test-driven development (TDD) and acceptance-test driven design, and is intended to make these practices more accessible and intuitive to newcomers and experts alike. It shifts the vocabulary from being test-based to behaviour-based, and positions itself as a design philosophy.

JBehave is a Java-based framework supporting Behaviour-Driven Development (BDD), an evolution of Test-Driven Development (TDD) and Acceptance-Test Driven Developement (ATDD).

BDD aims to make development practices more accessible and intuitive to newcomers and experts alike, but shifting the vocabulary from being test-based to behaviour-based. It positions itself as a development paradigm, emphasising communication and automation as equal goals.

You can find out more about Behaviour-Driven Development on the BDD wiki, or in the article Introducing BDD.

Last Release Year ['Active'=Current]:

Active

Since (maturity):

2003

JBehave
	Tool Scope	Test Automation Framework
	Application Rights	Free Use, Opensource
	Since	2003
	Company	GitHub project
	Support	Tool Support link HERE
	Download	Download HERE

Features

Pure Java implementation, which plays well with Java-based enterprises or when interfacing to any environment that exposes a Java API.
Users can specify and run text-based user stories, which allows "out-in" development.
User stories can be written in JBehave syntax or Gherkin syntax.
User stories can be specified as classpath resources or external URL-based resources.
User stories can be executed concurrently, specifying the number of concurrent threads.
User stories can be documented via generic user-defined meta information that allows easy story filtering and organisation into story maps.
Annotation-based binding of textual steps to Java methods, with auto-conversion of string arguments to any parameter type (including generic types) via custom parameter converters.
Annotation-based configuration and Steps class specifications
Dependency Injection support allowing both configuration and Steps instances composed via your favourite container (Guice, Needle, PicoContainer, Spring, Weld).
Groovy scripting supported for writing configuration and Steps instances
Extensible story reporting: outputs stories executed in different human-readable file-based formats (HTML, TXT, XML). Fully style-able view.
Story cross reference report format in JSON and XML, consumable by external applications.
Auto-generation of pending steps so the build is not broken by a missing step, but has option to configure breaking build for pending steps.
Pluggable step prioritising strategy. Strategies bundled in core include: by priority field and by Levenshtein Distance.
Localisation of user stories, allowing them to be written in any language.
IDE integration: stories can be run as JUnit tests or other annotation-based unit test frameworks, providing easy integration with your favourite IDE.
Ant integration: allows stories to be run via Ant task
Maven integration: allows stories to be run via Maven plugin at given build phase

JBehave modules

JBehave Core contains the core functionality of JBehave
JBehave Gherkin adds support for writing stories using the Gherkin syntax
JBehave Groovy adds support for writing steps using Groovy
JBehave Scala adds support for writing steps using Scala
JBehave Guice adds support for dependency injection using Guice
JBehave Pico adds support for dependency injection using PicoContainer
JBehave Spring adds support for dependency injection using Spring
JBehave Weld adds support for dependency injection using Weld
JBehave ODF adds support for stories written in ODF
JBehave Google adds support for stories stored in Google Docs
JBehave REST adds support for stories retrieved via REST API
JBehave Ant adds support for execution using Ant
JBehave Hudson Plugin adds support for execution using Hudson CI
JBehave Jenkins Plugin adds support for execution using Jenkins CI
JBehave Maven Plugin adds support for execution using Maven

jbehave-100px.png

Getting Started

Write a textual story

Create a textual story file with a name that expresses the behaviour to verify, e.g. i_can_toggle_a_cell.story and define steps in it:

Given a 5 by 5 game
When I toggle the cell at (2, 3)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (2, 4)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (2, 3)
Then the grid should look like
.....
.....
.....
.....
..X..

Steps must start with one of the keywords highlighted (see Concepts for more details) and are not limited to a single line. Also, unless otherwise indicated, a story has at least one implicit scenario, each of which is a collection of steps.

Map steps to Java methods

Define your GridSteps class, a simple POJO, which will contain the Java methods that are mapped to the textual steps. The methods need to annotated with one of the JBehave annotations and the annotated value should contain a regex pattern that matches the textual step:

public class GridSteps { // Look, Ma', I'm a POJO!
    
    private Game game;
    private StringRenderer renderer;
 
    @Given("a $width by $height game")
    @Aliases(values={"a new game: $width by $height"})
    public void theGameIsRunning(int width, int height) {
        game = new Game(width, height);
        renderer = new StringRenderer();
        game.setObserver(renderer);
    }
    
    @When("I toggle the cell at ($column, $row)")
    public void iToggleTheCellAt(int column, int row) {
        game.toggleCellAt(column, row);
    }
    
    @Then("the grid should look like $grid")
    @Aliases(values={"the grid should be $grid"})
    public void theGridShouldLookLike(String grid) {
        assertThat(renderer.asString(), equalTo(grid));
    }
 
}

Configure a Java Embeddable class

Define your Embeddable class which provides the link between the JBehave's executor framework (called Embedder) and the textual stories. The simplest configuration is a one-to-one mapping between a Java class and a textual story file. So we'll extend JUnitStory and give it a name that can be (conventionally) mapped to the textual story filename, e.g. ICanToggleACell.java:

public class ICanToggleACell extends JUnitStory {
 
    // Here we specify the configuration, starting from default MostUsefulConfiguration, and changing only what is needed
    @Override
    public Configuration configuration() {
        return new MostUsefulConfiguration()
            // where to find the stories
            .useStoryLoader(new LoadFromClasspath(this.getClass())) 
            // CONSOLE and TXT reporting
            .useStoryReporterBuilder(new StoryReporterBuilder().withDefaultFormats().withFormats(Format.CONSOLE, Format.TXT));
    }
 
    // Here we specify the steps classes
    @Override
    public InjectableStepsFactory stepsFactory() {       
        // varargs, can have more that one steps classes
        return new InstanceStepsFactory(configuration(), new GridSteps());
    }
}

The story is now configured to use the GridSteps that defines mappings between the textual steps and the Java methods to be executed.

Run story

Open your favourite IDE, the ICanToggleACell.java class will allow itself to run as a JUnit test. Be sure to check that you have all the required dependencies in your classpath.

View generated reports

Since we've defined two reports, CONSOLE and TXT, you should see during the running of the story the output being written the System.out. In addition, the same output will also have been written to a file in target/jbehave.

Important Questions

How do I use JBehave within my development environment?

Stories can be run on command-line (typically for continous-integration) or in any modern Java IDE that supports unit testing frameworks (JUnit supported by default, but any test framework can be easily adopted). Read more on running stories. Note that stories can also be run via web runner, although the web support is not part of JBehave Core. For more info on web support refer to JBehave Web.

Which testing frameworks does JBehave support?

JBehave comes bundled with out-the-box JUnit support but has no tie-in to JUnit. You can easily configure stories to run with other testing framework, such as TestNG or Spring's Test module (see developing stories for more details).

IDE can't seem to recognise the JUnitStory/Stories as a JUnit test

Some IDEs need to be aware of the JBehave source to enable the JUnit plugin for stories, as they can't spot the @Test annotation in a class jar. The link to the core sources is available from the download page. Alternatively, M2Eclipse users can downlaod the sources automatically.

Can I use annotations to configure my stories?

Yes, both annotated and programmatic configuration is supported. See configuration page for more details.

Can I insert comments in the textual scenarios?

Yes, at various levels:

In scenario title, which allows free text up the first step starting word of the scenario (e.g. the first Given), provided this is at the beginning of a line. Any keyword not at the beginning of a line, i.e. not preceded by a newline character, will be ignored.
Between executable steps, using keyword "!--" (which can be changed via i18n properties).
Between example table rows, using separator "|--".

JBehave-Web

JBehave is a collection of extension for JBehave that extend its capabilities in ways related to HTTP and the web.

Modules

Web-Selenium. Bindings to Selenium 1.0 and 2.0 allowing JBehave operate on web-sites.
Web-Runner. A web-app that allow the synchronous experimental running of stories for non-developers.
Web-Queue. A Web-interface for the enqueing of stories to be run later.

Depended-on Technologies

JDK required: 5.0 (or above)Maven required (2.2.1 or above, 3.0 or above for reporting).

IDE Integration

Maven is supported in Intellij IDEA out-of-the-box Maven is supported in Eclipse via m2eclipse plugin

Building

A regular Maven build will suffice:

mvn install

Maven Build Profiles

default: builds all releasable modules
examples: builds all headless examples

Maven Build Profiles used during release cycle

reporting: builds reports
distribution: builds distribution (documentation)

Note: profiles are additive and the default profile is always active.

Example Profile Usages

Build Core and all Examples

mvn install -Pexamples

Build with Reporting and Distribution

mvn install -Preporting,distribution

Building a Release with Maven

mvn release:prepare -Preporting,distribution 
mvn release:perform -Preporting,distribution

Presentation

Presentations

Click here to download the PDF file.

Files & Media

Media & Files

External Articles:

Simpler JBehave Examples Table Processing

Acceptance Tests with JBehave, Selenium & Page Objects

Behaviour-Driven Development

Codehaus project: jbehave

Testing REST content negotiation with jersey and jbehave

FAQs

Testing error handling in RESTful application with jersey and jbehave

JBehave Configuration Tutorial

Behavior-Driven Development (BDD) with JBehave, Gradle, and Jenkins

Automated Acceptance Testing with JBehave and Thucydides

Automate your integration tests

Automated Acceptance-Testing using JBehave

JBehave Plugin for IntelliJ

BDD with Scenario Code DSL – Sometimes you don’t need a tool

jbehave code and download on Github

Price Information

DISCLAIMER

In any case of miss-information between QATestingTools and the manufacturer call-center or website, the manufacturer price is the one you should take in consideration,the QATestingTools is NOT responsible for any miss-understanding or miss-information since we are NOT always informed on prices programs updates. In all cases please get more details from manufacturer.

KickOff Pricing:

Free use

Specifications

Tool Specifications

Application Rights:

Free Use

Opensource

Tool Scope:

Test Automation Framework

Testing Methods:

Acceptance testing

Agile testing

Automatic Testing

Behavior Driven Development

Test Driven Development

White Box testing

Tool Objectives:

Test Design

Operating Systems:

OS Independent

Scripting Language:

Gherkin Syntax

Groovy

Java

Scala

User Story

Supported Technologies:

REST

RESTful app

HTTP

Automation Tool Features:

Auto Complete

BDD Complex Steps

BDD Given Story

Binding Code

Built-in Reports

Hooks

Input External Data

RegExp Parameterize

Steps Prioritization

Tables Parameterize

Tagging

IDE Support:

Apache Ant

Eclipse

IntelliJ

Build Process Integration :

Hudson

Jenkins

User Interface Available:

Ant Integration

Command Line

Integrated into IDE

Maven Integration

Plugin

System Integration support:

ALM integration

Automation Tools Integration

IDE integration

Project Management integration

Reporting Formats:

HTML

JSON

TXT

XML

Training:

Documentation OnSite

External Information

FAQ

Manual

Comments

Some usefull links

Permalink Submitted by webmaster on July 28, 2012 - 17:59.

Some usefull links

Maven Repository http://mvnrepository.com/artifact/org.jbehave
Mven Plugin Documentation http://maven.apache.org/plugins/maven-site-plugin/plugin-info.html
Nexus Codehaus https://nexus.codehaus.org/content/repositories/releases/org/jbehave/
github jbehave https://github.com/jbehave
JBehave Jars http://mvnrepository.com/artifact/org.jbehave

MANUFACTURERS Wallboard

View MANUFACTURERS Wallboard

Testing tool manufacturers world-wide list
10Levels	ABID CONSULTING	AccelQ	Accord Software	ActiMind	AdaCore
AdaLog	AgileLoad	AgileWay	Agitar	Algorismi	ALL4TEC
Andreas Kleffel	Android	Apache	Apica	Apollo Systems	AppAssist.mobi
Applitools	AppPerfect	Appsee	ApTest	Assertible	Assure
Atlassian	AutoIt Consulti ..	Automation Anyw ..	Automation Cons ..	Axosoft	Aztaz Software
Backtrace I/O	Badboy	BlazeMeter	Borvid	BrowserStack	BSQUARE
BStriker Intern ..	CA Technologies	Canonical	Canoo Engineeri ..	Catch Software	CelestialTeapot
Chris Mallett	Cleanscape	ClicTest	CloudQA	Codeborne	CodeCentrix
CodePlex projec ..	Codoid	Cogitek	Compuware	Configure IT	Conflair
ConSol	Core Services	Coronys Ltd	Countersoft	CresTech Softwa ..	CrossBrowserTes ..
Crosscheck Netw ..	Crowdsourced Te ..	Cucumber Ltd	Cyara	Cygnet Infotech	DareBoost
Databene	Datamatics Glob ..	DevExpress	DTM soft	Dynatrace LLC	EasyQA
Eclipse	EkaTechserv	Elvior	Emmanuel Jorge	Empirix	EPAM Systems
Equafy	Esterel Technol ..	eXept Software ..	Experitest	Finaris	Froglogic
FrontEndART Ltd	GeneXus	GitHub project	gnoso	Google Code Pro ..	GrammaTech
Gurock Software	HelpSystems	HENIX	Hewlett Packard ..	Hexawise	High-Tech Bridg ..
Hiptest	Hitex	IBM Rational	imbus Shanghai	Impetus	Inflectra
informUp	InTENSO - IT Ex ..	Ipswitch	Jamo Solutions	Janova	JAR Technologie ..
JBoss Developer	jClarity	Jellly.io	JetBrains	Jively	jQuery foundati ..
JS Foundation	Jspresso	Kanoah	KMS Technology	Kualitee	LDRA Limited
Litmus	LoadFocus	Loadster Perfor ..	MarathonITE	Marketcircle	Marketcircle
Maveryx	Meliora Ltd	Micro Focus Sof ..	Microsoft	Mobile Labs	Mobile1st
Mockaroo, LLC	Monkop	Mozila	MSys Technologi ..	Navicat	NeoTys
Neowise Softwar ..	NetCart	NORIZZK.COM	Novosync Mobili ..	NRG Global	NTT Resonant
OC Systems	Odin Technology	OpCord	Oracle	Orcanos	Original Softwa ..
OW2	PANAYA	Parasoft	PassMark	Patterson Consu ..	Perfecto Mobile
Pivotal, Inc.	Plutora	Postman (API To ..	PractiTest	PrimaTest	Process One
Programming Res ..	Psoda	PureLoad	PushToTest	Python	Q-Assurance
QA Systems	QACube	QASymphony	QAWorks	QMetry	Quali
Qualitia Softwa ..	Quality First S ..	Quotium	RadView Softwar ..	Ranorex	RedLine13
Reflective Solu ..	ReQtest	RevDeBug	Robotium Tech	Rogue Wave Soft ..	Rommana Softwar ..
RTTS	ruby-doc.org	Runscope	Sandklef GNU La ..	Sauce Labs	Seapine Softwar ..
SeleniumHQ	Sencha	Sensiple	Siemens PLM Sof ..	SmartBear Softw ..	SmarteSoft
SOASTA	SoftLogica	Softomotive	Softsmith	Solution-Soft	SonarSource
Sourceforge	Spirent Technol ..	SQS Software Qu ..	Square	Stimulus Techno ..	Swifting AB
Synopsys	T-komp	T-Plan	TechExcel	TechTalk	Telerik By Prog ..
Tellurium	Test Collab	Test Goat	Test Recon	TestCaseLab	testCloud.de Gm ..
TestCraft Techn ..	Testenium	Testim.io	TestingBot	TestLodge	Testmunk
Testomato	TestOptimal	TestPlant	TestPro	Testsigma Techn ..	Testuff
The Core Bankin ..	The MathWorks	The Open Group	thePHP.cc	Thoughtbot	Thoughtworks
Tigris.org	Time Simulator	Top-Q	Trace Technolog ..	TrendIC	TRICENTIS
Tritusa Pty Ltd	TWD Solutions P ..	TypeMock	Tyto Software	Ubertesters	UniTESK
Universal Test ..	Usetrace Ltd	Utrecht Univers ..	Validata Group	Vanamco AG	Vector Software
Veracode	Verifaya Corpor ..	Verit	VersionOne	Viewlike.us	Vornex Inc.
Watir.com	WcfStorm Soluti ..	We Are Mammoth	Web Performance ..	Wintask	Wireshark Found ..
Worksoft	Xceptance	XK72	Xpand IT	XQual	ZAPTEST
Zeenyx Software ..	Zephyr	Zeta Software	zutubi pty

Acceptance-testing	Agile-testing
Application-Business-Logic	Automatic-Testing
Behavior-Driven-Development	Benchmark-testing
Black-Box-testing	Business-Flow-testing
Cloud-Based-Testing	Code-Coverage
Code-reviewing	Data-Driven-testing
Distributed-testing	End-to-End-testing
Exploratory-testing	Functional-testing
Hybrid-Testing	Integration-testing
Keyword-driven-testing	Load-Testing
Manual-testing	Model-Based-Testing
Monitoring	Object-Driven-Testing
Performance-testing	Regression-testing
Scalability-testing	Scrum-testing
Smoke-testing	Storyboard-testing
Test-Driven-Development	Traditional-Testing
Unit-testing	White-Box-testing

QATestingTools.com

Main menu

Tool Scope

Testing Methods

Testing Objectives

You are here

JBehave

Important Links

Tool Information

Tool Summary

JBehave is a Java-based framework supporting Behaviour-Driven Development (BDD), an evolution of Test-Driven Development (TDD) and Acceptance-Test Driven Developement (ATDD).

Features

jbehave-100px.png

Getting Started

Getting Started

Map steps to Java methods

Configure a Java Embeddable class

Run story

View generated reports

Important Questions

How do I use JBehave within my development environment?

Which testing frameworks does JBehave support?

IDE can't seem to recognise the JUnitStory/Stories as a JUnit test

Can I use annotations to configure my stories?

Can I insert comments in the textual scenarios?

JBehave-Web

Modules

Depended-on Technologies

IDE Integration

Building

Maven Build Profiles

Maven Build Profiles used during release cycle

Example Profile Usages

Build Core and all Examples

Build with Reporting and Distribution

Building a Release with Maven

Presentations

Media & Files

Price Information

DISCLAIMER

Tool Specifications

Comments

Some usefull links

MANUFACTURERS Wallboard