Frontier Frenzy Blog

Okay it took a fair bit of digging, but after [failing to get JBehave to work on the first attempt](http://blog.frontierfrenzy.com/post/43309958290/bdd-with-jbehave), I managed to stumble on something that works. Conclusion, JBehave is NOT straightforward to include in your project! I needed to make changes to the pom.xml and completely replace the PlayerStory class with a PlayerStories class **pom.xml** 4.0.0 modelVersion> com.frontierfrenzy game artifactId> 0.0.1 version> UTF-8 project.build.sourceEncoding> UTF-8 project.reporting.outputEncoding> 3.7.5 jbehave.version> 4.11 junit.version> de.codecentric jbehave-junit-runner artifactId> 1.0.1 version> junit junit ${junit.version} org.jbehave jbehave-core ${jbehave.version} org.apache.maven.plugins maven-compiler-plugin 2.3.2 version> 1.7 source> 1.7 target> org.jbehave jbehave-maven-plugin ${jbehave.version} run-stories-as-embeddables integration-test test scope> **/*Stories.java java.awt.headless true value> true ignoreFailureInStories> false ignoreFailureInView> run-stories-as-embeddables **\src\test\java\com\frontierfrenzy\model\test\PlayerStories.java:** package com.frontierfrenzy.model.test; import java.util.List; import org.jbehave.core.configuration.Configuration; import org.jbehave.core.configuration.MostUsefulConfiguration; import org.jbehave.core.io.CodeLocations; import org.jbehave.core.io.LoadFromClasspath; import org.jbehave.core.io.StoryFinder; import org.jbehave.core.junit.JUnitStories; import org.jbehave.core.reporters.Format; import org.jbehave.core.reporters.StoryReporterBuilder; import org.jbehave.core.steps.InjectableStepsFactory; import org.jbehave.core.steps.InstanceStepsFactory; import org.junit.runner.RunWith; import de.codecentric.jbehave.junit.monitoring.JUnitReportingRunner; @RunWith(JUnitReportingRunner.class) public class PlayerStories extends JUnitStories { @Override protected List storyPaths() { return new StoryFinder().findPaths(CodeLocations.codeLocationFromPath( "src/test/resources"), "**/*.story", "**/exclude_*.story"); } @Override public Configuration configuration() { return new MostUsefulConfiguration() .useStoryLoader( new LoadFromClasspath(this.getClass())) .useStoryReporterBuilder( new StoryReporterBuilder() .withFormats(Format. XML, Format.IDE_CONSOLE , Format.CONSOLE, Format.HTML, Format.TXT )); } @Override public InjectableStepsFactory stepsFactory() { return new InstanceStepsFactory(configuration(), new PlayerSteps()); } } Heres is my project layout so far: \src\main \src\test \src\main\java \src\main\resources \src\main\java\com \src\main\java\com\frontierfrenzy \src\main\java\com\frontierfrenzy\model \src\main\java\com\frontierfrenzy\model\Account.java \src\main\java\com\frontierfrenzy\model\Player.java \src\test\java \src\test\resources \src\test\java\com \src\test\java\com\frontierfrenzy \src\test\java\com\frontierfrenzy\model \src\test\java\com\frontierfrenzy\model\test \src\test\java\com\frontierfrenzy\model\test\PlayerSteps.java \src\test\java\com\frontierfrenzy\model\test\PlayerStories.java \src\test\resources\player.story Now when I run mvn verify I get this in the output (BeforeStories) [INFO] Running story player.story Story: Player can create a new account (player.story) Scenario: Story: Player can create a new account Narrative: As a player I want to be able to create a new player account So I can play the game Scenario 1: Given a player with email address [email protected] When he creates an account Then a new account is created (FAILED) (java.lang.AssertionError: ) (AfterStories)

In my [previous post in this series](http://blog.frontierfrenzy.com/post/43309253549/starting-out-with-bdd) I started some BDD work by writing some stories/scenarios. I'm from a Java background, so I'm going to be using JBehave to kick things off. The next step is to map the above scenarios to Java using JBehave Annotations. **src/test/java/com/frontierfrenzy/model/test/PlayerSteps.java** package com.frontierfrenzy.model.test; import org.jbehave.core.annotations.Given; import org.jbehave.core.annotations.Then; import org.jbehave.core.annotations.When; import org.junit.Assert; import com.frontierfrenzy.model.Account; import com.frontierfrenzy.model.Player; public class PlayerSteps { private Player player; private Account account; @Given("a player with email address $email") public void aPlayer(String email) { player = new Player(email); } @When("he creates an account") public void createNewAccount() { account = new Account(player); } @Then("a new account is created") public void checkAccount() { // Don't do anything for now Assert.fail(); } } Here I have mapped the Given/When/Then steps to methods that get executed when they are matched. Note that the Player & Account classes don't exist yet so this won't compile, so lets create them. **src/main/java/com/frontierfrenzy/model/Player.java** package com.frontierfrenzy.model; public class Player { private String email ; public Player(String email) { this .email = email; } } **src/main/java/com/frontierfrenzy/model/Account.java** package com.frontierfrenzy.model; public class Account { private Player player ; public Account(Player player) { this .player = player; } } Okay having written that initial model, I'm not sure I've gotten the relationship correct, but I'm going to leave it for now until I come across a requirement that isn't supported by it. Next step is to get this running as part of my unit tests, I'll be extending JBehaves JUnitStory class which seems to do the wiring between JUnit and JBehave. As far as I can tell, the simplest implementation is as follows: public class PlayerStory extends JUnitStory { @Override public Configuration configuration() { return new MostUsefulConfiguration(); } } Which picks up my Player story file. Final step is to setup Maven to pull in the dependencies and run the tests. I thought I might be able to just have a pom with JBehave in it along with JUnit and the tests would get picked up as part of the test phase. Reading around that doesn't seem to be the case, but let me try it.... 4.0.0 modelVersion> com.frontierfrenzy game artifactId> 0.0.1-SNAPSHOT org.apache.maven.plugins maven-compiler-plugin 2.3.2 version> 1.7 source> 1.7 target> UTF-8 project.build.sourceEncoding> UTF-8 project.reporting.outputEncoding> org.jbehave jbehave-core 3.7.5 version> junit junit 4.11 version> Yep when I run mvn test it doesn't work. Back to the drawing board for my [next post]().

_Disclaimer – This blog series is going to be fairly raw in that I’m going to capture my thoughts as they go through my head, while I am working and see how it turns out in code. You have been warned. I don’t claim to be an expert on BDD so you will likely see bad practices on the way. As these get highlighted to me (either through readers’ comments or self-realization) I’ll update the post as appropriate._ I’m having a go at using BDD to develop an application from scratch. I’m aiming to build a game, but to start with I’m going to write some fairly generic stories which could apply to any application that allows users to sign up and login. I’m going to start by just capturing the titles of my stories, and then dive in to expand on them in more detail as I progress. Stories: 1. Player can create a new account 2. Player can login 3. Player can logout 4. Player can manage his account These 4 stories are going to form my backlog and I’m going to deal with them in that order with #1 being highest priority and so on. Iteration 1 will tackle the first story, so let’s get on with it and expand it out using the “As a…I want…So that” pattern that is recommended as the approach to take [see http://dannorth.net/introducing-bdd/] Story: Player can create a new account Narrative: As a player I want to be able to create a new player account So I can play the game Scenario 1: Given a player with email address [email protected] When he creates an account Then a new account is created I will need to add in things for incorrect email address's and for players that already exist that sort of thing, but we will stick with this relatively simplistic version for now, but we will expand as we progress. The [next post in the series](http://blog.frontierfrenzy.com/post/43309958290/bdd-with-jbehave) will expand on this scenario and get some code going.