Adventures of a wannabe geek!

Ranting within

Moving From Cuke4Nuke to Specflow

For the past few years I have been annoying introducing all of the people I have worked with to automated testing. The tool I showed was Cuke4nuke. Now this has been a great tool for me. Its a way to run Cucumber style tests written in code (read more about it at the link above)

I think the time has come for me to finally move away from this. This is no reflection on the product itself, I think Richard Lawrence has done a fantastic job on the product, but the reason I’m moving away from the product is that it is no longer feasible for me to be able to run my tests using a ruby console. The team I currently work with are having trouble with ruby installations etc. so I made the decision to move to Specflow as it’s a BDD tool.

What advantages will specflow give me over cuke4nuke?

1st, and the main advantage, is that the tests written with specflow can be run directly from Visual Studio Unit test sessions. For my test this is very important as we are trying to get the tests run on a regular basis as they do their work.

2nd the developers will no longer need to have a ruby installation. For me, having Ruby isn’t too much of an issue as I’m interested in learning it and looking at it, but for other developers they see this as a bit of a chore to run the tests via ruby console and command line.

3rd is that the developers who run the tests can debug the tests themselves as they are running inside the Visual Studio environment. Again I’m not saying that tests always need debugged but it helps them when it’s needed

I’ll still be keeping an eye on the project as I have very much enjoyed using it. I guess my thanks have to go to Richard Lawrence and Goyko Adzic for blogging about the product and its uses