Since the 0.9.6 release of easyb, new members have joined the development team, a number of new features have been added, more than a few issues have been addressed, and the easyb community of projects continues to evolve! For those of you living on the bleeding edge, you can build 0.9.7 from the trunk; conversely, an official 0.9.7 release is forthcoming.
In the meantime, here’s some of the hip news coming from the front lines of easyb development:
- easyb now has an Eclipse plugin!
- There’s a new XMLUnit plugin, which facilitates using XMLUnit along with easyb
- There are new wiki pages documenting, for example, how to create easyb plugins, how to use the XMLUnit plugin, and how to leverage Mockito
- As a new feature, underscores are no longer needed when defining shared behaviors (i.e. the keywords are now
shared behavioralthough the keywordshared_behaviorstill is valid - You can now obtain a print out of story text without executing them
- unexecuted stories will be marked as “in-review”
- The keyword “but” is now supported
- it technically works just like “and” and was added to support further readability of scenarios
- There’s a new maven plugin release
- simply update your POM and you’ll be good to go
- There has also been a new release of the easyb IntelliJ plugin
- easyb now works with IntelliJ 9.0
- you can find the new version in IntelliJ’s Plugin Manager
- There is a new project dubbed easyb-junit, which “provides a way to run easyb behaviors through JUnit”
- The popular Griffon project has an easyb plugin (this plugin has been available for quite some time)
- There have been improvements made to the easyb Grails plugin as well as documentation enhancements
- Using easyb with Gradle has been documented
- A number of issues have been closed including 145, 165, 168, 169, 133
- easyb now builds against Groovy 1.7.0
Indeed baby, these are fun times for easyb! Many thanks to the community for its continuing enthusiasm and help — the easyb team can’t do it without you.
If you want to get involved, join the mailing list, suggest features (or document defects), follow the project on Twitter, and spread the good news!
