Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
FIT and JBehaveThe Good, the Bad and the Ugly<br />Practical Agility<br />Lightning Talk<br />Sep 2, 2010<br />
Why These Two?<br />
FIT<br />FITLibrary / SLIM<br />Fitnesse<br />
HTML Tables In<br />HTML Tables Out<br />
Fixtures<br />
Wiki<br />
Ease of Use<br />
Existing Features<br />(Selenium, DBFit)<br />
Versioning<br />Partitioning<br />
Low-Level Fixtures<br />
Stakeholder Readability<br />
MethodNamesThatGoOnForeverOrUntilThePropsEnd<br />
The “Parse” Problem<br />
Difficult to do Test First<br />
JBehave<br />
Plain-Text Story<br />Given/When/Then<br />(Story and Scenarios)<br />
Steps Classes with<br />Annotations / Regex<br />
Story Class (optional)<br />as bridge from<br />Story (text) to Steps<br />
Flow for Agile<br />(Test First)<br />(Defines Done)<br />
Text From Anywhere<br />
Configuration API<br />Oddities<br />
No Tags for You!<br />
Reporting<br />
! (JUnit | TestNG)<br />
What features would <br />the ideal ATDD framework have?<br />
Upcoming SlideShare
Loading in …5
×

FIT and JBehave - Good, Bad and Ugly

5,318 views

Published on

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

Notes available in the PPTX.

Published in: Technology

FIT and JBehave - Good, Bad and Ugly

  1. 1. FIT and JBehaveThe Good, the Bad and the Ugly<br />Practical Agility<br />Lightning Talk<br />Sep 2, 2010<br />
  2. 2. Why These Two?<br />
  3. 3. FIT<br />FITLibrary / SLIM<br />Fitnesse<br />
  4. 4. HTML Tables In<br />HTML Tables Out<br />
  5. 5. Fixtures<br />
  6. 6. Wiki<br />
  7. 7. Ease of Use<br />
  8. 8. Existing Features<br />(Selenium, DBFit)<br />
  9. 9. Versioning<br />Partitioning<br />
  10. 10. Low-Level Fixtures<br />
  11. 11. Stakeholder Readability<br />
  12. 12. MethodNamesThatGoOnForeverOrUntilThePropsEnd<br />
  13. 13. The “Parse” Problem<br />
  14. 14. Difficult to do Test First<br />
  15. 15. JBehave<br />
  16. 16. Plain-Text Story<br />Given/When/Then<br />(Story and Scenarios)<br />
  17. 17. Steps Classes with<br />Annotations / Regex<br />
  18. 18. Story Class (optional)<br />as bridge from<br />Story (text) to Steps<br />
  19. 19. Flow for Agile<br />(Test First)<br />(Defines Done)<br />
  20. 20. Text From Anywhere<br />
  21. 21. Configuration API<br />Oddities<br />
  22. 22. No Tags for You!<br />
  23. 23. Reporting<br />
  24. 24. ! (JUnit | TestNG)<br />
  25. 25. What features would <br />the ideal ATDD framework have?<br />

×