Comments on: An Evolution of Test-Specification Styles – My Journey to MSpec

By: Joshua Gough

Joshua Gough — Mon, 19 Sep 2011 04:40:00 +0000

This was very very helpful. Thank you.

By: Awkward Coder » How to MSpec?

Awkward Coder » How to MSpec? — Tue, 13 Apr 2010 22:19:13 +0000

[...] An Evolution of Test-Specification Styles – My Journey to MSpec [...]

By: Internal DSL Becomes External DSL « Making the Complex Simple

Internal DSL Becomes External DSL « Making the Complex Simple — Wed, 10 Mar 2010 15:33:35 +0000

[...] was wondering about some of the tools we use that are using internal DSLs. This post prompted me to think about it more deeply, which prompted this post, which ultimately lead me here. [...]

By: Elegant Code » Is MSpec an Internal DSL?…And is that okay?

Elegant Code » Is MSpec an Internal DSL?…And is that okay? — Wed, 03 Mar 2010 20:27:12 +0000

[...] my last post on MSpec, John Sonmez commented: When I see the MSpec code, I think about it being an internal DSL for doing the testing, and I [...]

By: Jirapong Nanta

Jirapong Nanta — Wed, 03 Mar 2010 17:20:47 +0000

This is awesome. Very clear step by step of thinking to use mspec. I has been use mspec for my work (TDD.NET cc.net) . It just worked.

Thank you for this kind of article.

By: Richard Cirerol

Richard Cirerol — Wed, 03 Mar 2010 15:22:44 +0000

@John Sonmez, Glad to hear this post helped you out.

I think that you are spot-on when you call MSpec an internal DSL. Chris Brandsma and I had a similar conversation yesterday morning.

Look for another post soon on this topic. (Thanks for the inspiration!)

By: Dan Jensen

Dan Jensen — Tue, 02 Mar 2010 22:17:18 +0000

@Richard Cirerol Richard, it seems to have magically fixed itself. I had another task to address, and when I came back to this it was somehow working. Gotta love that. Thanks for the article!

By: John Sonmez

John Sonmez — Tue, 02 Mar 2010 20:29:26 +0000

First off… Richard, thank you so much providing an example that shows me just how MSpec and xUnit type code differs. That is a very good easy to understand example, and really helped me to understand what MSpec is trying to do.

I’m still not sure though. I can see both points. When I see the MSpec code, I think about it being an internal DSL for doing the testing, and I start to think that perhaps it should just go ahead and be it’s own language instead of trying to live inside of C#. On the other hand, I wonder about the value of using another language to unit test C# code, so I can see Chris’s point there.

By: Richard Cirerol

Richard Cirerol — Tue, 02 Mar 2010 17:59:21 +0000

Dan, I haven’t had any issues using the SpecificationFor class with Behaviors. Would you be willing to share the problem code?

By: Dan Jensen

Dan Jensen — Tue, 02 Mar 2010 16:34:14 +0000

I really like your SpecificationsFor style base class, and so I tried out a similar approach. It works for most of my specs, but I have a few which use Behaviors, and I keep getting failures because it tells me the SUT is null. I’m guessing MSpec is failing to wire up the SUT in the behaviors with the generic one in my base class. Did you run into this problem, and were you able to overcome it?