Comments on: Cucumber, A Brief Overview http://lostechies.com/joeybeninghove/2010/06/01/cucumber/ Just another LosTechies site Fri, 15 Oct 2010 23:08:45 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Atom http://lostechies.com/joeybeninghove/2010/06/01/cucumber/#comment-138 Atom Mon, 07 Jun 2010 21:43:52 +0000 /blogs/joeydotnet/archive/2010/06/01/cucumber.aspx#comment-138 Hey great article. I am a ROR programmer, NEW, but still ror and my experience with .net is nil. This article really helped shed some light, thank you! Hey great article.

I am a ROR programmer, NEW, but still ror and my experience with .net is nil.

This article really helped shed some light, thank you!

]]> By: Andrew http://lostechies.com/joeybeninghove/2010/06/01/cucumber/#comment-137 Andrew Wed, 02 Jun 2010 07:27:07 +0000 /blogs/joeydotnet/archive/2010/06/01/cucumber.aspx#comment-137 There is anothoer .Net option: NGourd. It works in a similar way - plain english tests which are executed using methods marked up with regex attributes. It reports using NUnit XML format, which is awsome because the tests can contribute to the continuous integration build. It's open source. There is anothoer .Net option: NGourd. It works in a similar way – plain english tests which are executed using methods marked up with regex attributes.
It reports using NUnit XML format, which is awsome because the tests can contribute to the continuous integration build.
It’s open source.

]]> By: Darren http://lostechies.com/joeybeninghove/2010/06/01/cucumber/#comment-136 Darren Wed, 02 Jun 2010 01:16:55 +0000 /blogs/joeydotnet/archive/2010/06/01/cucumber.aspx#comment-136 A few of us at my employer have had some success with SpecFlow, which is about as close as you can get to Cucumber on .Net. Other than Cucumber on IronRuby, I guess... but still the same thing. We've used it successfully in three places so far: 1.) Acceptance testing. We have one project manager who has really taken to Gherkin specs. We'll sit down and write the specs, then a coder will implement the step definitions. It's almost magical how well it has worked out. 2.) Integrations. I don't mean integration testing, I mean testing and explaining integrations. Things like importing data files, credit card transactions, etc. Just about any time you have to dial out to another service. Even though these tests usually employ mocks, they provide a great explanation for those who need to find the bridge between the different systems. 3.) Complex unit-tests. I've found that if using Cucumber/SpecFlow for unit testing can quickly get out of hand But in a few places where a little English would help to express what's going on, it works. This especially is true for ASP.Net MVC controllers. A few of us at my employer have had some success with SpecFlow, which is about as close as you can get to Cucumber on .Net. Other than Cucumber on IronRuby, I guess… but still the same thing.

We’ve used it successfully in three places so far:

1.) Acceptance testing. We have one project manager who has really taken to Gherkin specs. We’ll sit down and write the specs, then a coder will implement the step definitions. It’s almost magical how well it has worked out.

2.) Integrations. I don’t mean integration testing, I mean testing and explaining integrations. Things like importing data files, credit card transactions, etc. Just about any time you have to dial out to another service. Even though these tests usually employ mocks, they provide a great explanation for those who need to find the bridge between the different systems.

3.) Complex unit-tests. I’ve found that if using Cucumber/SpecFlow for unit testing can quickly get out of hand But in a few places where a little English would help to express what’s going on, it works. This especially is true for ASP.Net MVC controllers.

]]>