Each week, Marketplace Monday profiles one (or two) great add-ons available in the Atlassian Marketplace–where you can try and buy more than a thousand add-ons for Atlassian products. Holy smokes! AtlasCamp 2012 is almost upon us, and it’s our first big milestone since we launched the Marketplace back at Summit 2012 on June 1. To celebrate three and a half months of Marketplace, this week we’ll be profiling add-ons and Atlassian partners every day up until AtlasCamp kicks off. Today’s post features not one add-on, but two. We’ll cover Behave for JIRA, our winner for Best Marketplace-paid Add-on in the Codegeist 2012 plugin development competition, and the runner up in that category, Image Slider for Confluence. Behave for JIRA Overview Behave for JIRA is a tool for agile testing and requirements discovery within JIRA. It allows users to express required functionality as “acceptance criteria” for use in acceptance test driven development. If you’re not familiar with ATDD, it’s also known as “specification by example,” an agile testing method where automated acceptance criteria are defined early in the development cycle and used in the development process itself, rather than as validation after testing is completed. As John Ferguson Smart writes in JavaWorld, Traditionally, testers will prepare test plans and execute tests manually at the end of the software development phase…ATDD takes a different approach. Essentially, ATDD involves collaboratively defining and automating the acceptance tests for upcoming work before it even begins — a simple inversion that turns out to be a real game changer. Rather than validating what has been developed at the end of the development process, ATDD actively pilots the project from the start. Who It’s For Behave for JIRA is for Product owners to define requirements early in the development cycle and attach them to user stories, which is critical to establishing the real requirements in the product and responding to customer demands. Developers, who can use Gherkin to define tests and automate them with Cucumber, speeding up the development process by clarifying requirements and ensuring that written code has the functionality customers want. Testers, who can read tests in natural language and understand the entire context of the code, and can track any broken functionality up to the scenario level. How It Works The Behave for JIRA add-on works by adding an “Acceptance Tests” field to JIRA issues. When users click the “add” icon in the acceptance test section, they are given a window where they can add acceptance tests to the issue–these scenarios are then grouped into features. Once users create scenarios and add them to features (which can be linked to multiple JIRA issues), they can use Gherkin to define the steps of the scenario. Once step definitions are in place in JIRA, users configure Maven and Cucumber. Then, when mvn verify is run, Maven extracts the acceptance tests from JIRA and they are run by Cucumber. It’s also possible to run the tests manually. The X Factor Atlassian Bamboo and the Cucumber Report Plugin make Behave for JIRA even more powerful. This plugin allows Bamboo to pull in reports [...]