From WPF functional Unit Tests to Specifications using MSpec and White

I am in the train back home and wanted to try out quickly to migrate our WPF functional tests written has Unit Tests to BDD Specifications.

Here is the code I started from, pure Unit Test using NUnit and White

[Test]
 public void Opening_Valid_VersionZip()
 {
     OpenAndWait("Product.zip");
 
     Assert.That(MainWindow.Title.Equals("Product.zip - Innoveo Skye® Editor"));
     Assert.That(Status.Text.Equals("product"));
     Assert.That(ProductTree.Nodes.Count >= 1);
     Assert.IsFalse(SplashScreen.Visible);
     Assert.IsTrue(SaveButton.Enabled);
     Assert.IsTrue(ActivateButton.Enabled);
 }

Now the same functional test written as a BDD specification using MSpec

[Subject("OpenVersionZip")]
 public class when_user_open_valid_versionzip : MainWindowViewSpecs
 {
     Establish context = () => {};
 
     Because of = () => OpenAndWait("Product.zip");
 
     It should_display_mainwindow_title_correctly = () => 
         MainWindow.Title.ShouldEqual("Product.zip - Innoveo Skye® Editor");
 
     It should_display_status_correctly = () => 
         Status.Text.ShouldEqual("product");
 
     It should_display_the_product_tree = () => 
         ProductTree.Nodes.ShouldNotBeNull();
 
     It should_hide_the_splashscreen = () => 
         SplashScreen.Visible.ShouldBeFalse();
 
     It should_enable_save_button = () => 
         SaveButton.Enabled.ShouldBeTrue();
 
     It should_enable_activate_button = () => 
         ActivateButton.Enabled.ShouldBeTrue();
 }

And the output in ReSharper MSpec plugin

4687909611_49a4e5a71a_o[1]

Which one do you prefer? I personally have made my choice.

An article by Laurent Kempé

No Comments

May
19
2010

Watin // MSpec // Jobping

ASP.NET MVC 2, MSpec and Watin

The other day I posted about “Automated functional tests using Watin and MSpec” which we do at Jobping as a spike to automate our functional tests on our ASP.NET MVC 2 site.

Yesterday evening I was facing an issue in my base class WebBaseSpec which led to really strange side effects. Basically when I was running one unit test alone it was Green, running all or more than one unit test will fail miserably with the well known STA issue of Watin.

So I thought that I had an issue with the ReSharper MSpec plugin but after some discussion with Alexander GroßI realized that the second failing test was showing another issue than the STA issue.

Going further I realized that when I was checking the following

It should_direct_user_to_aboutus_page = () => 
     Browser.Uri.Route().ShouldMapTo<HomeController>(x => x.About());

First I needed to call the ASP.NET MVC RegisterRoutes

MvcApplication.RegisterRoutes(RouteTable.Routes);

which was done in the constructor of my WebBaseSpec class.

protected WebBaseSpec()
 {
     MvcApplication.RegisterRoutes(RouteTable.Routes);
     InitBrowser();
 }

That’s was the problem, I was registering the routes several time, one time per test. So first one was ok, second one was failing…

So I modified it to the following, ensuring that the routes were registered only one time!

private static bool registered;
 
 /// <summary>
 /// Initializes a new instance of the <see cref="WebBaseSpec"/> class.
 /// </summary>
 protected WebBaseSpec()
 {
     if (!registered)
     {
         MvcApplication.RegisterRoutes(RouteTable.Routes);
         registered = true;
     }
     InitBrowser();
 }

Now I can run all my functional tests again

4621024158_d2c99039a0_o[1]

An article by Laurent Kempé

No Comments

About Laurent

Laurent Kempé is the editor, founder, and primary contributor of Tech Head Brothers, a French portal about Microsoft .NET technologies.

He is currently employed by Innoveo Solutions since 10/2007 as a Senior Solution Architect and certified Scrum Master.

Founder, owner and Managing Partner of Jobping, which provides a unique and efficient platform for connecting Microsoft skilled job seekers with employers using Microsoft technologies.

Laurent is awarded by Microsoft since Avril 2002: Most Valuable Professional (MVP).