Announcing xBehave.net 1.0
It gives me great pleasure to announce the release of xBehave.net 1.0.
This is the first stable release of xBehave.net after more than 18 months of (sporadic) initial development. Extensive documentation is also now available on the xBehave.net wiki.
By far the most important aspect of xBehave.net is you, the community. Thank you for all the contribution, usage, suggestion, bug discovery, criticism and discussion. It has made xBehave.net what it is today. Please continue so xBehave.net can continue to evolve as we do.
In particular, I’d like to thank the following developers for their contributions to xBehave.net 1.0:
The roots of xBehave.net go back to August 2008 in a spike by Phil Haack and Brad Wilson named SubSpec, aimed at showcasing the extensibility of xUnit.net.
The idea was rekindled in August 2010 by Johannes Rudolph when he created the SubSpec project, later published on NuGet.
In January 2012, Cameron Fletcher introduced the original SubSpec spike to a project we were working on. Although I’d previously read Phil Haack’s post, I’d never tried the code until then. I immediately liked it and, having already used Cucumber with Ruby, I soon stumbled upon the idea of introducing a Given, When, Then syntax to the library.
Soon afterwards I discovered and forked Johannes Rudolph’s SubSpec project and created SubSpecGWT which I pushed to NuGet in early February 2012.
After a month of development and a few more releases, I re-branded the project as xBehave.net and pushed the first release to NuGet at the end of February 2012.
Over the next 18 months the library became richer and more polished and gained a few contributors in the march up to 1.0.
After a little tweeting in May 2013 Glenn Block decided to use xBehave.net for acceptance test examples in his forthcoming book ‘Designing Evolvable Web APIs with ASP.NET’.
The next planned version is 2.0 which will see a transition from xUnit.net 1.9 to xUnit.net 2.0 (currently in alpha).
1.0 has entered maintenance mode with bug fix releases only. All new features will be scheduled for 2.0 or later.
Internally, the changes in 2.0 will be significant. xUnit.net 2.0 is more or less a complete re-write, which means xBehave.net 2.0 is likely to be the same.
If you’d like to help out, just head over to the GitHub repository where you can get familiar with the code, send pull requests or raise issues for new features, bugs, questions, discussions etc.
You can also ping me on Twitter or in the xBehave.net chat room on JabbR.