Skip to main content

Specflow

After listening to .Net Rocks with Scott Millett this week I felt a renewed enthusiasm for trying out some BDD. I downloaded Specflow and got straight on with the screen cast they have on their website. The video acts as a good introduction into how to get up and running in Specflow. Interestingly it also gave me a better insight into how bowling works. I have never really thought about it. I normally just wang the balls down the lane until the game is over!

Specflow introduces the idea of writing the specification first. It uses a specific language called Gherkin which comes from Ruby land. You will need NUnit installed as well. An example of it is: 

[edit: NUnit is what I have used up to now but Specflow is compatible with other testing frameworks aswell. See the comments section below.]

Feature: Passwords

In order to have a strong password
As a new user or existing user changing my password
I need to check if my password is alphanumeric and is greater than 6 characters

Scenario: Password only comprises of characters

Given I have entered "nottinghamforest" as my new password
When I press save
Then the system should reject the password
And say "The password must be alphanumeric and greater than 6 characters"

It's a fairly straight forward language. Although I really want to use it for a new asp.net mvc project I have in mind and I am not quite sure how to write out features and scenarios for things like "The user clicks on the drivers link and can then view a list of current drivers on the system...". I am currently cruising the Google Group for Specflow though and have spotted a couple of examples that might help me.  I have previously been doubtful of Specflow and this specification malarky before, favouring just writing unit tests in a certain way instead. For example WhenCreatingANewPassword.ThePasswordMustBeAlphaNumeric. However after messing about with this for 2 days I can really see where this might come in useful. 

I had a go at my own clean version of BDD using Specflow by making a very simple password strenght checker project. The winning thing about it? I wrote the spec on my netbook in notepad++ last night whilst watching Terminator 2. No coding was done. I then brought it into work this morning, put the feature file in. Added the steps file (which was very short because I reused them with regex helpers) and then implemented what I needed to do. I could really see the benefit if you had a client that had a domain expert that was also a bit of a power user. They could easily get into the rythm of writing / amending features for your project.

I have uploaded it to GitHub (which is also a first for me!). So you can check it out there.
https://github.com/DominicFinn/Specflow-Example-Password-Strength

Comments

Dom Finn said…
Thanks, I will definitely check that out. The MSTest support will be handy as (for right or wrong) I am currently using that in quite a few projects.

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second