bgeek.net: NSpecify => RSpec… well closer anyway
maruismarais
· 1 year ago
Firstly, I'd like to thank you for your contributions to the NSpecify project. I really like the Context, BeforeEach, etc synonyms that you've added. The lambda support you've added is also pretty cool.
In the future I plan to introduce extension methods to allow specifying on the object itself. I actually did a prove of concept a while back. The problems I found was that you can't have the following syntax
user.Must.Not.Allow(user.Save).With.Error("A user must have a name before being saved");
but rather as follows
user.Must().Not.Allow(user.Save).With.Error("A user must have a name before being saved");
which I don't mind.
I'm working on a Auto Test library and Notifier application. I have an almost stable version and if you are interested, let me know. With this application I plan to have the same sort of specdoc to be displayed (as in rspec on TextMate). Maybe in the browser, I'll see when I get there...
My only problem at the moment is I'm stuck in .NET 2.0 land in my day job, so my understanding and exploration of 3.5 features suffers at the moment...
All Comments
In the future I plan to introduce extension methods to allow specifying on the object itself. I actually did a prove of concept a while back. The problems I found was that you can't have the following syntax
user.Must.Not.Allow(user.Save).With.Error("A user must have a name before being saved");
but rather as follows
user.Must().Not.Allow(user.Save).With.Error("A user must have a name before being saved");
which I don't mind.
I'm working on a Auto Test library and Notifier application. I have an almost stable version and if you are interested, let me know. With this application I plan to have the same sort of specdoc to be displayed (as in rspec on TextMate). Maybe in the browser, I'll see when I get there...
My only problem at the moment is I'm stuck in .NET 2.0 land in my day job, so my understanding and exploration of 3.5 features suffers at the moment...