Comments on: Introducing xUnit.BDDExtensions

By: My First Journey into BDD - Scott Densmore's Blog -

My First Journey into BDD - Scott Densmore's Blog - — Sun, 15 Feb 2009 23:22:44 +0000

[...] BDD Frameworks MSpecSpecUnitNSpecxUnit.BDDExtensions [...]

By: Alexander Zeitler

Alexander Zeitler — Wed, 04 Feb 2009 20:49:41 +0000

Hi Björn,

just fyi: it runs out of the box with cc.net when configuring cc.net according to http://www.codeplex.com/xunit/Wiki/View.aspx?title=HowToUseCcNet

Alex

By: BjRo

BjRo — Wed, 04 Feb 2009 16:58:39 +0000

Hey Ben,

fixed it. Sloppy me. Thank you.

Björn

By: Ben Taylor

Ben Taylor — Wed, 04 Feb 2009 14:35:53 +0000

Hi Björn,

xUnit.BDDExtensions looks interesting.

I have just tried to get latest and build the source. However, the project is missing a file called DependencyOptions.cs. Actually, the project includes the file, but the file is not in the repos. Please can you add it?

I will cross-post this to the GC issues list too.

Ben

By: BjRo

BjRo — Wed, 04 Feb 2009 08:58:30 +0000

I’m not a CC.NET user, so I can’t answer that question with certainty.
What I can say for sure is xunit.console.exe runs xUnit.BDDExtensions out of the box. Same applies to Resharper.
I’ll look into the MSBuild task today or tomorrow, in order to detect what might be wrong. Shouldn’t be too hard to fix . . .

By: Alexander Zeitler

Alexander Zeitler — Tue, 03 Feb 2009 22:22:23 +0000

Hi,

will xUnit.BDDExtensions work with CC.NET and xUnit Build Taks for MSBuild out of the box? My Build log always shows:

Summary
Tests run: 0 Failures: 0, Skipped: 0, Run time: 0s

By: admin

admin — Wed, 15 Oct 2008 16:54:03 +0000

Interesting idea. Never thought of that. Implementing that using Because() as the only test method on the fixture class shouldn’t be that difficult, too.

The only problem I currently see is that I’m not able to use the Resharper Test Explorer in meaningful ways anymore (because it would only display the Because() method and not the Observations). The current approach works fine in both TD.NET and Resharper…

By the way: Very interesting blog, you’re on my list now

By: Colin Jack

Colin Jack — Wed, 15 Oct 2008 14:16:14 +0000

I’m wondering why you’ve chosen for EstablishContext to be called before each test. With such cut-down specifications, and where the specifications just assert (no side affects), why not just have the setup of the fixture and the action on the SUT done once?

By: BjRo

BjRo — Mon, 06 Oct 2008 08:36:21 +0000

AAA imho is more a clean layout for tests, than a good wording for specifications.

By: Sergey Shishkin

Sergey Shishkin — Mon, 06 Oct 2008 07:37:39 +0000

1. In my opinion, CleanupSpecification looks the same technically as Dispose. You hide this method behind the base class anyway.

2. The need to explain how EstablishContext, CreateSut and Because correspond to AAA indicates the lack of intent revealing. What about that?

[Concern(typeof(SpecificationTestCommand))]
public class when_a_specification_test_command_is_executed_on_a_ITestSpecification_implementer :
concern_for_specification_test_command
{
…

protected override SpecificationTestCommand Arrange()
{
…
return new SpecificationTestCommand(innerCommand, methodInfo);
}

protected override void Act()
{
testResult = Sut.Execute(testSpecification);
}

[Assertion]
public void should_ask_the_test_specification_to_initialize()
{
testSpecification.WasToldTo(x => x.InitializeSpecification());
}
}