Recent Blog Posts

  • Competition and Knowledge-Sharing
    By Johanna Rothman - Wednesday Aug, 27
    In Knowledge Management Needs to be Agile, Too, I said If you put people in competition with each other *in any way*, they will have dis-incentives to share their knowledge. John, in his comment on ... more »
  • Test Automation Class in Virginia
    By Jared Richardson - Monday Aug, 25
    The first scheduled class for the NFJS One venture is now official! And we don't even have the website live yet. :) This class will be a good mix of the "Why" as well as the "How". The goal is for yo... more »
  • ReadWriteWeb on Dirty Data
    By Michael Nygard - Sunday Aug, 24
    A short while back, I did a brief series on the value of "dirty data"---copious amounts of unstructured, non-relational data created by the many interactions user have with your site and eac... more »
  • rspec_validation_expectations gem released
    By Matthew Bass - Friday Aug, 22
    I just released a new gem on GitHub that provides some common validation expectations to rspec. Instead of writing specs to verify that your models are handling validation correctly, these expectation... more »
  • “Seeing Your Work” Podcast Posted
    By Johanna Rothman - Friday Aug, 22
    I’ve posted my “Seeing Your Work” podcast. It’s available on libsyn and through iTunes. If you’d like me to interview you or you interview me, lemme know. ... more »

easyb 0.9 hits the streets

Posted by: Andrew Glover on 06/30/2008

announcement!
The easyb team is pleased to announce the release of easyb 0.9, baby!

The 0.9 release has:

easyb supports capturing additional hip information regarding stories, such as a story’s description and some detail regarding the features, benefits, and roles of a persona related to a story. For instance, the DSL now supports a description syntax that takes a String value — single quote or Groovy’s triple quote trick.

description "some description"
scenario "text"

or

description """some long description that requires
multiple lines, etc
"""
scenario "text"

What’s more, you can provide additional details of a story via the narrative syntax:

description "text"

narrative "description", {
 as_a "role"
 i_want "feature"
 so_that "benefit"
}

scenario "text"

Both the narrative and description keywords are optional and they don’t have to be used together– i.e. you can use the narrative one without providing a description. These aspects will be captured in the output (i.e. story report) of an easyb run too.

From a fixture standpoint, easyb supports both one time fixtures (before) and for each scenario (before_each). Of course, you can add tearDown-like behavior in after and after_each.

You can download the latest release from easyb’s Google code page.

Have a listen to JavaWorld's Java Technology Insider


be the first to rate this blog


About Andrew Glover

Andrew Glover is the President of Stelligent Incorporated, which helps companies address software quality with effective developer testing strategies and continuous integration techniques that enable teams to monitor code quality early and often.

Andrew was the founder of Vanward Technologies, which was acquired by JNetDirect in 2005. He is the co-author of Addison Wesley's "Continuous Integration", Manning's "Groovy in Action" and "Java Testing Patterns". He is an author for multiple online publications including IBM's developerWorks and Oreilly's ONJava and ONLamp portals. He actively blogs about software quality at thediscoblog.com and testearly.com.

More About Andrew »