Hot off the NuGet press, it’s the first preview release of SpecsFor.Mvc 4.0!   This release introduces more configurability, exposes more state for your tests to examine, and (hopefully) greatly improves the initial setup experience by removing a lot of frustration.

[more]

Here’s a quick rundown on what’s change. 

FluentField<T> now supports asserting off its value fluently:

SUT.FindFormFor<LogOnModel>()
    .Field(m => m.UserName).ValueShouldEqual("[email protected]")
    .Field(m => m.Password).ValueShouldEqual(string.Empty);

The temporary directory that your application is published to can now be overridden.  This makes it possible to spin up multiple integration hosts with multiple websites for more advanced testing scenarios. 

var site1Config = new SpecsForMvcConfig();
site1Config.UseIISExpress()
    .With(Project.Named("Website1"))
    .WithTemporaryDirectoryName("Website1TempDir");

var site1Host = new SpecsForIntegrationHost(site1Config);

var site2Config = new SpecsForMvcConfig();
site2Config.UseIISExpress()
    .With(Project.Named("Website2"))
    .WithTemporaryDirectoryName("Website2TempDir");

var site2Host = new SpecsForIntegrationHost(site2Config);

site1Host.Start();
site2Host.Start();

You cannot directly utilize MVC 5.1’s attribute routing from a test project due to some nasty infrastructure in that stack, but that’s ok, because SpecsFor.Mvc now has a workaround.  Just call the BuildRoutesUsingAttributeRouting… helper method, and point it at your web project:

site1Config.BuildRoutesUsingAttributeRoutingFromAssemblyContaining<HomeController>();

Similar to SpecsFor, SpecsFor.Mvc now has a friendly post-install page to help you get started:

image

There are also numerous improvements to help you get up and running with less pain:

  • An exception is thrown if you forget to specify a BrowserDriver. 
  • The Selenium WebDriver executables are now pulled in via external NuGet packages.  These packages have a much better mechanism of acquiring and referencing the WebDriver executables than SpecsFor.Mvc previously had.
  • SpecsFor.Mvc now checks for the required version of Microsoft Build Tools when you install the NuGet package.  If they are not installed, you’ll get a nice warning and some instructions on how to install them. 
  • SpecsFor.Mvc now uses the latest version of MSBuild.  This should eliminate a lot of strange cases where a project compiles fine in Visual Studio but doesn’t publish correctly when tests are executed.

I think that about covers it.  Go try out the latest pre-release package, and let me know if you run into any problems!