Behat = Awesome.

It is behavior-driven development framework for PHP.

What is behavior-driven development, you ask?

• Step 1: Write human-readable sentences

• Step 2: Describe a feature of your application and how it should work

• Step 3: Implement this behavior in software.

• Step 4: ?!?!??

• Step 5: Profit

What Behat requires?

Behat requires alot of things to be awesome.

It requries upfront prep work from the client and developer

Requires direct access to source code

What we need?

• To hide the complexity of behat steps and to make it easier on clients.

• To keep the Behat feature files in source control

• And still keep the good stuff the Behat Provides in terms of automation.

Solutions Out There

JiraExtenstion

How it works?

Clients will write behat features in Jira

Then you can run these tests by executing the following command:

vendor/bin/behat @app jira-SKI:51

Pros/Cons

Updated JiraExtention: How it works?

How it works?

• Write feature files with ticket as tag

• Execute Behat, and watch jira for feature files pushed up

How it works?

Feature files are pushed to readonly fields for clients to read and accept. Jira is then used a point of disscussion for these features. Modifications are made by the developer till an agreement is made.

Pros/Cons