Easy Spec

EasySpec uses annotations to define the unit of interest, context, and behaviors for BDD-style specifications. Because there is no test runner, you are free to use your favorite. We are currently dogfood-ing this with Groovy and Java test runners. Specifically, we're using the GroovyTestCase on our Groovy projects and JUnit 4 with our Java projects. Easy Spec is independent of the testing framework.

Latest News

• Documentation has been greatly extended (12/16/2008)
• Examples are complete and documented (12/16/2008)
• 0.2 released with an improved command line interface (12/16/2008)

Examples

Examples are now available and documented. There are examples on this wiki as well as full example projects in both Java and Groovy.

Currently Supported Features:

• Reflect over a test .jar and parse out behaviors
• Generate an HTML report showing implemented and unimplemented behaviors.
• Allow filtering of packages to limit which classes in the .jar are checked for having the @EasySpec annotation

See ReleaseNotes

Upcoming Features

• Better Error Handling
• Handle incomplete specification classes by reporting errors in the output report
• Allow interest to be a class
• Space out the humps in the class name for reporting the interest

Questions

Be sure to check out these pages:

• Glossary of Terms
• Basic Easy Spec description
• The Usage Guide
• Examples

Feel free to email any questions that you have: easyspec (at) gmail.com

My blog (which will be seeing more BDD content) can be found at: testinfected.net

Patches are welcomed.