fit and jbehave - good, bad and ugly
DESCRIPTION
A 6 minute lightning talk at Sep 2, 2010 Practical Agility session in Minneapolis MN (DevJam). Notes available in the PPTX.TRANSCRIPT
FIT and JBehaveThe Good, the Bad and the Ugly
Practical AgilityLightning TalkSep 2, 2010
Why These Two?
FITFITLibrary / SLIM
Fitnesse
HTML Tables InHTML Tables Out
Fixtures
Wiki
Ease of Use
Existing Features(Selenium, DBFit)
VersioningPartitioning
Low-Level Fixtures
Stakeholder Readability
MethodNamesThatGoOnForeverOrUntilThePropsEnd
The “Parse” Problem
Difficult to do Test First
JBehave
Plain-Text StoryGiven/When/Then
(Story and Scenarios)
Steps Classes withAnnotations / Regex
Story Class (optional)as bridge from
Story (text) to Steps
Flow for Agile(Test First)
(Defines Done)
Text From Anywhere
Configuration APIOddities
No Tags for You!
Reporting
! (JUnit | TestNG)
What features would the ideal ATDD
framework have?