Rob’s Tech Blog

StoryQ sounds really good, nice work on pushing it out under the MIT licence. I think I need to read up on some of the awesomeness that LINQ provides.
Still yet to use BDD in practice, so I’m really keen on hearing the easyb.org talk at the Java Emerging Technologies conference (http://java.meetup.com/162/calendar/8313099/).

Have you read ‘xUnit Test Patterns’ by Gerard Meszaros?
I’ve got it sitting next to me right now, really want to dedicate some time to read it in full.

I’ve heard of it, haven’t read it though. Give me a good summary when you are done

Hey Rob. Was gonna take a look at your silverlight slides and came across this. BDD sounds very interesting indeed, I think I will read more about it.

Interesting – the Eleutian guys have been doing something similar with MSpec:

http://blog.eleutian.com/SearchView.aspx?q=mspec

I still only dabble with BDD – but haven’t become a complete convert yet – I’m thinking MSPec or StoryQ could push me over the edge

Hi, I cant seem to access the code/sample page. Can someone please provide a link?

Hi Mark

The wiki links on the storyQ home page seem broken. I totally blame Codeplex. Todd & I will look into that and send you an email when its fixed. Thanks for checking out our project – we’re actually slowly doing some awesome background work on it now.

Cheers – Rob

Looks really great, really love the way it integrates so easily.

Any plans to support Actions with parameters and a catalog of actions like NBehave?

Hi Roger

Thanks!

Could you please give me some examples of what a catalog of actions is? Parameterised actions do work, as long as your parameters have reasonable ToString() implementations

Hi Rob,

What I had in mind for the catalog of actions was something like the example in http://www.codeplex.com/NBehave/Wiki/View.aspx?title=Examples&referringTitle=Home

where the first usage of a “given, when or then” stores the implementation (the delegate) and it can be used again, with different parameter values, specifying just the name (description).

However, I see now your usage pattern is a little different. I guess your use of an expression tree means that simple expressions (and not statement lambdas) are required – and so you probably don’t have a strong need to remember the implementation (as it is usually a one-liner).

Given all that, maybe it would be useful to combine the functionality of your two buttons in your UI tool to offer a third button that generates code that uses the Expression overloads of the Given,When,Then,And methods. Could have private stub implementations of the expressions.

Roger

Hi Roger

I was reading your comment and thinking “yes that’s brilliant”, when I realised that that feature’s already there .

If you tick the “Declare Method” checkbox, then the GUI will generate expression calls instead of strings. You can then use Visual Studio’s smart tags or Resharper to generate the method stub.

Cheers – Rob

Hi Rob,

didn’t work for me… checking “Declare Method” resulted in this:

>>>
[Test]
public void ()
{
…
<<>>
…
.WithScenario(“”)
.Given(“That “)
.When(““)
.Then(“”)
<<>>
.WithScenario(“”)
.Given(() => ThatA())
.When(() => b())
.Then(() => c())
<<<

Roger

Hi Rob,

trying again, coz the formatting went a bit bad with my angle brackets…

didn’t work for me… checking “Declare Method” resulted in this:

– start of code snippet –
[Test]
public void ()
{
…
}
– end of code snippet —

but I still had this:

– start of code snippet –
.WithScenario(”s”)
.Given(”That a“)
.When(”b“)
.Then(”c”)
– end of code snippet –

when what I really wanted was this:

– start of code snippet –
.WithScenario(”s”)
.Given(() => ThatA())
.When(() => b())
.Then(() => c())
– end of code snippet –

I do like your idea of relying on Resharper or VS to help out instead of having the StoryQ UI tool generate stubs, as generating stubs suggests a pattern of usage that you probably don’t want to recommend.

Roger

I’m new to both StoryQ and TeamCity.

How do you configure TeamCity to display the html reports from StoryQ nicely?

@Martin

Integrating reports into TeamCity is a two step process:
1. Make sure that you are creating the html report for each method. This means using the story.AssertAndReportToFile(MethodBase.GetCurrentMethod());

2. In team city, add them project > General Settings > Artifact Path > **/*.html => storyq (something like that)

I hope that helps.

[...] think this is a good opportunity to talk about some of the new features in StoryQ. My first post on StoryQ came when we’d just committed it to codeplex, and a lot has changed since [...]