• AddRunAsAdministratorToSlnFilesInShell.reg.txt
• AddRunAsAdministratorAsDefaultToSlnFilesInShell.reg.txt

sut.WhenIn(States.Loading)
 .On(Commands.Next)
  .Do(() => Console.WriteLine("got next command while loading..."))
  .Do(() => Console.WriteLine("doing it again..."))
 .On(Commands.Previous)
  .Do(() => Console.WriteLine("got previous command while loading..."));

sut.WhenIn(States.Ready)
 .On(Commands.Previous)
  .Do(() => Console.WriteLine("got previous command while ready..."));

So how should we define our methods to accomplish this initialization style? Let’s begin with identifying the methods we need.

• WhenIn(TSTate state)
• On(TCommand command)
• Do(Action action)

Next thing to do is analyze in which sequence these methods can be called:

Ok, now that we have clarified the requirements a little we can start working on a solution. Let’s start with defining an interface for each of the methods:

interface IChooseState<TState, TCommand> { Q1 WhenIn(TState state); }
interface IChooseCommand<TState, TCommand> { Q2 On(TCommand command); }
interface IChooseAction<TState, TCommand> { Q3 Do(Action action); }

From WhenIn we need to be able to call On. Thus Q1 = IChooseCommand<TState, TCommand>. Q2 is also easily solved because from On we only have to be able to call Do, thus Q2 = IChooseAction<TState, TCommand>.

From Do we should be able to call both On and Do. We can do that by defining another interface which has both methods:

interface IChooseCommandAndAction<TState, TCommand> : IChooseCommand<TState, TCommand>, IChooseAction<TState, TCommand> { }

Now that we have found answers for Q1, Q2 and Q3 we can define the API for initializing our StateMachine as following:

IChooseCommand<TState, TCommand> WhenIn(TState state);
IChooseAction<TState, TCommand> On(TCommand command);
IChooseCommandAndAction<TState, TCommand> Do(Action action);

Now tell me about your strategy for implementing a fluent interface!

• Not all versions of Visual Studio are capable of running the tests.
• Test inheritance is not supported.
• Running tests via mstest.exe is slow.
• Visual Studio creating tens of .vmsdi files.

There are already a couple of better frameworks out there, and currently MbUnit is my favorite one, certainly in combination with TestDriven.NET.

I have created a custom implementation of the Microsoft.VisualStudio.QualityTools.UnitTestingFramework assembly. Actually, the assembly only has a couple of Attributes for the moment but contributions are always welcome

In order to achieve better performance i decided to implement a custom test runner. Currently Gallio uses mstest.exe but there might be a day that i decide to write a plugin so that mytestrunner can be used instead.

I was inspired by Creating Self-testing Assemblies and decided to use that approach but for some odd reason visual studio insists on running unit tests although the assembly is a console application Anyway, i can still invoke mytestrunner via the external tools as following:

The source code is available at http://code.google.com/p/mytestrunner/.

/// <summary>
/// When comparing instance with null, instance should be greater.
/// </summary>
[TestMethod]
public void ShouldReturnPositiveWhenComparedWithNull()
{
 $classname$ value = new $classname$("0");
 Assert.IsTrue(value.CompareTo(null) > 0);
}

Anyway, feel free to download the corrected IntValueObject and StringValueObject templates.

Simply save IntValueObject.zip and StringValueObject.zip under %My Documents%\Visual Studio 2005\Templates\ItemTemplates and click on “Add New Item” in your project:

Add the bottom of the dialog you can choose one of the templates:

Here is the result of adding an International Standard Book Number class:

Apparently (here and here) the VS2005 Developer edition is missing a couple of libraries that the VS2005 Tester edition adds to the testrunconfig. If your tests don’t depend on these, the simplest way to solve this problem is to remove all the values nodes, and their childnodes, where the type is defined in the Microsoft.VisualStudio.QualityTools.LoadTest, Microsoft.VisualStudio.QualityTools.WebTest and Microsoft.VisualStudio.QualityTools.LoadTest.WebStress assemblies.