Screencast: Testing Web Applications in .NET with Cuke4Nuke and WatiN

Yesterday, I released Cuke4Nuke 0.2.2, which added WatiN compatibility and an example of how to use the two tools together. Here’s a short screencast in which I walk through the example:

Resources from the video:


Leave a Reply

Your email address will not be published. Required fields are marked *

  1. Hi Richard

    I like the cucumber concept alot. Its my favourite tool for test at the moment.

    However I’m not that keen on the implementation. I find the ruby cucumber test runner slow (esp under IronRuby), cryptic, and frustrating. And another problem is that for lots of .Net people is that they get frightened of the ruby part. their loss I’m sure but you know what some people are like!

    So where I’m going with this comment is: what are your thoughts on a fully native .net runner? Maybe even with a GUI to tempt all those windows developers?


    • @Mike – The point of the wire protocol implementation we used for cuke4nuke was to avoid IronRuby, precisely because it’s slower than MRI (the normal Ruby interpreter). If IronRuby were fast enough, we would have used it the same way cuke4duke uses JRuby to run Java step definitions in-process. Aslak is talking about doing an all-Java version cuke4duke to remove the Ruby dependency there. I may do the same for .NET after seeing how that works out. For now, running cuke4nuke with IronRuby is far from optimal. I recommend using MRI instead.

      For an all-.NET alternative today, you might look at SpecFlow, a cucumber-style tool that uses the same Gherkin parser. They’ve focused heavily on Visual Studio integration, so you might find the runner more to your liking (it generates unit tests, so you just use any unit test runner).

    • @MF – It depends very much on how your application is designed and at what level you’d like to automate it. I have one client who tests their C/C++ app from Ruby Cucumber via a Ruby to custom-RPC interface they created. Others test their app through a service layer. I don’t know whether there are libraries to automate MFC apps through the GUI. The bottom line is that if you can drive your app somehow from Ruby, Java, or C#, you can test it with Cucumber. Step definitions are essentially just methods.

Richard Lawrence

Is co-owner of Agile For All. He trains and coaches teams and organizations to become happier and more productive. He draws on a diverse background in software development, engineering, anthropology, and political science. Richard is a Scrum Alliance Certified Enterprise Coach and Certified Scrum Trainer, as well as a certified trainer of the accelerated learning method, Training from the Back of the Room. His book Behavior-Driven Development with Cucumber is due out from Addison-Wesley later this year.

Connect Twitter LinkedIn Subscribe to RSS Feed Blog posts by this author