Development with EASYB Drive

Before you start

About this tutorial

EASYB is a behavior-driven development (BDD) framework for the Java™ platform. Easyb uses a standards-based DSL, with the goal of supporting executable, readable documentation. All you need to do is write the EASYB specification in Groovy and execute them with Java run programs that can be invoked from the command line, Apache Maven 2, or Apache Ant. With Easyb, you can more easily verify the behavior of any program written in Java code.

Goal

This tutorial progressively guides you through the use of EASYB and uses cases to collaborate with stakeholders. You will learn how to:

Use stakeholder vocabulary to define cases and scenarios

Implement them with EASYB

The real purpose of test-driven development (TDD) through BDD practice

After completing this tutorial, you will understand the benefits of collaboration cases implemented with EASYB and how this framework makes collaboration easier.

Prerequisite

To take full advantage of this tutorial, you should be familiar with the basic concepts of object-oriented development on Java syntax and Java platforms. You should also be familiar with refactoring and general unit testing.

System Requirements

To practice and test the code for this tutorial, you need to install one of the following products:

Sun ' s JDK 1.5.0_09 (or later)

Ibm®developer Kit for Java technology 1.5.0 SR3

You also need easyb and Apache Ant. This tutorial provides download links and installation instructions for EASYB and Ant.

For this tutorial, the recommended system configuration is:

Systems that support Sun JDK 1.5.0_09 (or later) or IBM jdk 1.5.0 SR3 with at least 500MB of primary memory

At least 20MB of disk space for installing software components and related examples

The instructions and examples in this tutorial are based on the microsoft®windows® operating system. All of the tools mentioned in this tutorial can also be run on linux® and UNIX® systems.

Requirements and results do not match

The gap between the people who define software requirements (stakeholders) and the people who implement the software requirements (developers) is long-standing. Most of the flaws in the software are related to the need for misunderstanding, regardless of the platform or application. Most businesses are plagued by software mismatch requirements-even if corporate stakeholders think they have expressed their needs well before.

In recent years, a number of commercial and open source solutions have emerged to address this problem. In terms of open source, there are fit and fitnesse frameworks. They try to bridge this gap by allowing stakeholders to write specifications (in tabular format) and then implement tests that enable developers to run these custom requirements. However, if you take a moment to understand such a framework, you will find that the gap still exists. The problem is in the medium used to define the requirements.