views:

423

answers:

3

For instance if I wanted to unit test the following controller what do I replace ???? with?

using System.Web.Mvc;
namespace MvcApplication1.Controllers
{
    public class StatusController : Controller
    {
        public ActionResult Index()
        {
            return Content("Hello World!");
        }
    }
}


[TestMethod]
public void TestMethod1()
{
    // Arrange
    var controller = CreateStatusController();

    // Act
    var result = controller.Index();

    // Assert
    Assert.AreEqual( "Hello World!.", ????);
}
+2  A: 

You cant test that the result is not null, that you recieve a ContentResult and compare the values:

[TestMethod]
public void TestMethod1()
{
    // Arrange
    var controller = CreateStatusController();

    // Act
    var result = controller.Index();

    // Assert
    Assert.NotNull(result);
    Assert.IsAssignableFrom(typeof(ContentResult), result);
    Assert.AreEqual( "Hello World!.", result.Content);
}

I apoligize if the Nunit asserts aren't welformed, but look at it as pseudo-code :)

Luhmann
+1  A: 

use the "as" operator to make a nullable cast. Then simply check for a null result

[TestMethod]
public void TestMethod1()
{
    // Arrange
    var controller = CreateStatusController();

    // Act
    var result = controller.Index() as ContentResult;

    // Assert
    Assert.NotNull(result);
    Assert.AreEqual( "Hello World!.", result.Content);
}
CVertex
+1  A: 

I like creating assertion helpers for this sort of thing. For instance, you might do something like:

public static class AssertActionResult {
    public static void IsContentResult(ActionResult result, string contentToMatch) {
        var contentResult = result as ContentResult;
        Assert.NotNull(contentResult);
        Assert.AreEqual(contentToMatch, contentResult.Content);        
    }
}

You'd then call this like:

[TestMethod]
public void TestMethod1()
{
    var controller = CreateStatusController();
    var result = controller.Index();

    AssertActionResult.IsContentResult(result, "Hello World!");    
}

I think this makes the tests so much easier to read and write.

Seth Petry-Johnson
That's a great idea Seth. I have quite a few of the ContentResult unit tests to code so this will help on trying to keep to the DRY philosophy .
Nicholas Murray
@Nicholas: Glad you found it helpful. Other helpers I have are `AssertActionResult.IsRedirectTo(result, url)` and `AssertActionResult.IsViewResult(result, viewName)`.
Seth Petry-Johnson