Question: Can you guys install it? I am not sure about whether that is a connectivity problem for me...
![enter image description here](https://i.stack.imgur.com/nskRA.png)

Answer: 
Controller should be tested that they return correct ActionResult in your case, and the Success or Failure of ActionResult should be tested by ActionResultTest and it has nothing to do with controller. Unit test means single unit test - but you test both controller and ActionResult in the same test, that is incorrect. To test ActionResult, first imagine that generally all that ActionResult does, is writing result to HttpResponse. Let's rewrite your code to use [Moq](http://nuget.org/List/Packages/Moq) to supply `StringWriter` for `ControllerContext.HttpContext.HttpResponse.Output`

```
[Test]
    public void Valid_input_returns_success_result()
    {
        var result = controller.Test(new TestModel { IsValid = true, IsValid2 = true })
            .AssertResultIs<FormActionResult<TestModel>>();

        var context = controller.ControllerContext;

        Mock<HttpContextBase> mockHttpContext = new Mock<HttpContextBase>();

        StringWriter actionResultOutput = new StringWriter();

        mockHttpContext.Setup(x => x.Response.Output).Returns(actionResultOutput);

        context.HttpContext = mockHttpContext.Object;

        result.ExecuteResult(context); 
        // how to verify result? Examine actionResultOutput

    }

```

All is left to examine actionResultOutput. For example, if your action result is designed to return string "Success" when validation is ok and "Error" when validation failed, compare these strings to `actionResultOutput.ToString()`. If your result view's generated html is more complex, you can use [HtmlAgilityPack](http://htmlagilitypack.codeplex.com/) to examine output more deeply
You should write a simple unit test of the Test-action, asserting on the returned action result. You shouldn't depend on the MVC framework in your test. Simply create a new instance of TestController and call the Test method.