Email
Favorite
Favorited ×
Download
Embed
Private Content
Copy and paste this code into your blog or website Copy Customize Close
We have emailed the verification/download link to "".
Login to your email and click the link to download the file directly.

To request the link at a different email address, update it here. Close
Validation messages. Success message. Fail message.

Check your bulk/spam folders if you can't find our mail.

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

+ Follow

FIT and JBehave - Good, Bad and Ugly

by brianrepko on Sep 15, 2010

1,994 views

A 6 minute lightning talk at Sep 2, 2010 Practical Agility session in Minneapolis MN (DevJam).

More…

A 6 minute lightning talk at Sep 2, 2010 Practical Agility session in Minneapolis MN (DevJam).

Notes available in the PPTX.

Less

Statistics

Favorites: 1
Downloads: 27
Comments: 2
Embed Views: 0
Views on SlideShare: 1,994
Total Views: 1,994

1–2 of 2 previous next

brianrepko @mike-at-gd - yes, those were added after this presentation - I'm actually a big fan of (and contributor to) JBehave so part of my criticisms were for things that I knew it needed 12 months ago Reply
Are you sure you want to Yes No
mike-at-gd #22 is not absolutely right
http://jbehave.org/reference/stable/meta-filtering.html here is the tags 1 year ago Reply
Are you sure you want to Yes No

Both are ATDDBoth are pure JavaThey are the only 2 that I’ve worked with on projects
FIT is the core library – HTML tables as data – parsing the table calls into a Fixture object’s methodsFITlibrary / SLIM – libraries for fixture developmentFitness – a test management and execution tool
FIT input is HTML tables and output is HTML tables (styled)
Table/Row/Column maps to method in fixture class
Fitnesse is a wiki – allows for add/edit/delete/run as well as meta/text for tests
Easy to use – has been around for a while
Easy to drive a web UI with SeleniumFixtureEasy to populate or verify database state with DBFit
Partitioning your tests in Fitnesse by “state” is toughTag/Branch test w/ code is tough with FitnesseFitnesse creates zip files for versioning
Want to code test based on functionality and not UIDB is pre/post conditionToo brittle for refactoring – want to use the fixtures in my own fixtures
Hard to think in “tables” (particularly when they are parsed differently)
Model is not Table, Row and Column which are all ParseableAll are modeled as a ParseParse is a verb not a noun – really hard to read the APISurprisingly, the FIT code was listed in one book as a “superbly designed API”In the end – its hard to write fixtures
Spend lots of time on the “design of the fixture” rather than the actual tests
JBehave 3 in particular
Story text is plain-text (UTF-8) with i18n’d keywordsScenarios are Given/When/Then format
Steps classes are POJOs with annotated @Given(regex), @When(regex), @Then(regex) methodsRegex is matched against text in the storySteps classes are like a library of fixtures
Story class can map the Story text to the set of Steps classes needed for itCan also be used to say when a story is “included in the execution suite”
Tests don’t run until Story class exists (one way to run)Scenarios are used to define done – and can actually be written early
JBehave can load the story text from anywhere – any source that BA/QA folks use (and can be versionable)
Some strange use of fluent language and builder patternsStrange API around Embedder and Embeddable
No tags per story / scenario (yet)Useful for conditional execution
Have to do this by hand – built-in reporting types require custom code (see examples)
A story (with all its scenarios) is one test methodCan’t run just one scenarioNo ability to monitor like JUnit/TestNG does for test classes/methods

1 Favorite

Kyle Liu , Java Developer at home 2 months ago

FIT and JBehave - Good, Bad and Ugly — Presentation Transcript

FIT and JBehaveThe Good, the Bad and the Ugly
Practical Agility
Lightning Talk
Sep 2, 2010
Why These Two?
FIT
FITLibrary / SLIM
Fitnesse
HTML Tables In
HTML Tables Out
Fixtures
Wiki
Ease of Use
Existing Features
(Selenium, DBFit)
Versioning
Partitioning
Low-Level Fixtures
Stakeholder Readability
MethodNamesThatGoOnForeverOrUntilThePropsEnd
The “Parse” Problem
Difficult to do Test First
JBehave
Plain-Text Story
Given/When/Then
(Story and Scenarios)
Steps Classes with
Annotations / Regex
Story Class (optional)
as bridge from
Story (text) to Steps
Flow for Agile
(Test First)
(Defines Done)
Text From Anywhere
Configuration API
Oddities
No Tags for You!
Reporting
! (JUnit | TestNG)
What features would
the ideal ATDD framework have?

FIT and JBehave - Good, Bad and Ugly

by brianrepko on Sep 15, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

FIT and JBehave - Good, Bad and Ugly — Presentation Transcript