Java EE Behave!!!!

Java EE Behave!!!!
Behaviour-Driven Development with Java EE

Aaron Walker
a.walker@base2services.com
@aaronwalker
http://aaronwalker.me
http://www.base2services.com
#jeebehave
base2Services Pty Ltd Commercial in Conﬁdence 2010

Agenda
• What is this BDD thingy
• JBehave
• How to make your tests behave!
• { Demo }

• Java EE ﬂavouring
• { Demo }

• Q &A
#jeebehave
base2Services Pty Ltd 2011

BDD
~ Behaviour Driven Development ~

“BDD facilitates agile development, which is an
approach to develop functional software, within
reasonable timeline, making everyone happy,
without killing anyone, or
burning down any bank.”

#jeebehave

BDD's Core Principles
• It's all behaviour
“The business & technology people should be
speaking the same words when referring to the
same idea,there should not be any translator.”
Behaviour: the addition of N values should yield the
summation of them

Example: the addition of 2 + 4 + 2 should yield 8

#jeebehave

BDD's Core Principles

• The evolution of test-driven development
(TDD) and acceptance-test driven design
• Shifts the vocabulary from being test-based
to behaviour-based
• Essentially a design philosophy

#jeebehave

Unit testing
frameworks mismatch
It’s all about the Behaviour

#jeebehave

Oh JBehave
• a framework for Behaviour-Driven
Development.

• pure Java implementation

• Users can specify and run plain text-
based user stories

• Annotation-based conﬁguration and
Steps class speciﬁcations

• Dependency Injection support (more
on this one later)

• Tool/IDE integration

• Ant, Maven, Selenium, Eclipse, IntelliJ,
Netbeans

#jeebehave

Yep....plain text

#jeebehave

Narrative
• Describes the overall intent of the story
• Generally describes a single feature or use
case
• Should include any participating actors
“In order to learn about BDD and JBehave as
a JavaOne attendee I will attend session
24421- JEE Behave!”
#jeebehave

Scenario

• Describes a speciﬁc interaction
• Generally ﬁne-grained
• test valid and invalid outcomes

• Support for parametrisation
“Scenario: User signs up with invalid data”

#jeebehave

Given|When|Then|And
• Given ... setting up system to a known
state
• When ... exercising an event
• Then ... verifying an outcome
• And ... used to chain multiple Given, When
and Then statements

#jeebehave

So where’s the Java?
• Mapping Textual Scenario Steps to Java Methods via
annotations
• Steps instances may inherit or implement other class/
interface as required by the model of the application under
test.
• allows many different ways to configure Embeddable Java
classes
• ConfigurableEmbedder: allows the specification of the
Configuration and CandidateSteps.
• InjectableEmbedder: allows the injection of a fully specified
Embedder.
#jeebehave

JUnit
• JUnit is supported out-of-the-box via several
Embeddables implementations:
• JUnitStory: provides a one-to-one mapping
with the textual story via the
StoryPathResolver.
• JUnitStories: provides a many-to-one
mapping with the textual story paths
explicitly speciﬁed by overriding the
storyPaths() method.
#jeebehave

One Step at a time

#jeebehave

And the conﬁg
• Fluent API for specifying conﬁguration

#jeebehave

{ Demo }
Enough Slide-ware
Show me the Code!!!

#jeebehave

Now lets sprinkle a
little bit of JEE on top

#jeebehave

CDI/Weld

• Contexts and Dependency Injection for
Java
• (JSR-299 included in JEE6)

• Weld is the reference implementation
• http://seamframework.org/Weld

#jeebehave

JBehave CDI support
• jbehave-weld module
• Uses Weld Java-SE integration to bootstrap the CDI
container

• can inject configuration and steps using
CDI annotations
• greatly simplifies the configuration and
management of step classes
#jeebehave

Inject the Configuration
• Use a CDI @Produces along with a
@WeldConfiguration qualifier annotation
• Gets automatically injected into the running
scenario

#jeebehave

What about the Steps
• Simply mark Step classes with a @WeldStep
annotation
• They get automatically added as candidate steps
• Steps can use @Inject to inject dependencies

#jeebehave

{ Demo }
Show me a better way!!!

#jeebehave

JBehave Web
• JBehave Web is an extension of the JBehave
framework providing a web integration layer
• Features include:
• Web Queue to allow generic stories to be run asynchronously
via a simple web interface.

• Web Runner to allow generic stories to be run synchronously
via a simple web interface.

• Selenium integration module to allow automation of stories
for web applications using Selenium.
#jeebehave

{ Demo }
Now let’s put all this together

#jeebehave

System Integration
Testing
• JBehave is a good language for describing
system integration
• BA’s, QA’s, architects, and developers are all
speaking the same language
• Self documented acceptance tests
#jeebehave

What’s Next

• Custom CDI Scopes
• @StoryScope, @ScenarioScope
• Arquillian Integration
• ???????
#jeebehave

Q &A
• http://behaviour-driven.org/
• http://jbehave.org - JBehave project site
• github.com/aaronwalker/JavaOne2011 -
demo code
• http://aaronwalker.me - blog
• a.walker@base2services.com - email
• @aaronwalker - twitter
#jeebehave

Java EE Behave!!!!

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (6)

Ähnlich wie Java EE Behave!!!!

Ähnlich wie Java EE Behave!!!! (20)

Mehr von Aaron Walker

Mehr von Aaron Walker (12)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Java EE Behave!!!!