TestBase.AdoNet 4.0.5.2

TestBase gets you off to a flying start when unit testing, especially for projects with dependencies on AspNetMvc, HttpClient or Ado.Net It has rich, yet so easily extensible, fluent assertions, including EqualsByValue, Regex, Stream Comparision, Ado.Net,Mvc and HttpResponseMessage assertions.

Fluent Assertions

Chainable fluent assertions get you to the point concisely

UnitUnderTest.Action()
    .ShouldNotBeNull()
    .ShouldContain(expected);
UnitUnderTest.OtherAction()
    .ShouldEqualByValue(new {Id=1, Payload=expected, Additional=new[]{ expected1, expected2 }} )
    .Payload
        .ShouldMatchIgnoringCase(""I expected this"");

* ShouldBe(), ShouldMatch(), ShouldNotBe(), ShouldContain(), ShouldNotContain(), ShouldBeEmpty(), ShouldNotBeEmpty(), ShouldAll() and many more
* ShouldEqualByValue(), ShouldEqualByValueExceptForValues() works with all kinds of object and collections
* Stream.ShouldHaveSameStreamContentAs()` and `Stream.ShouldContain()

Testable Logging with StringListLogger:

MS Logging: ILoggerFactory factory=new LoggerFactory.AddProvider(new StringListLoggerProvider())
Serilogging: new LoggerConfiguration().WriteTo.StringList(stringList).CreateLogger()
//
var logger=new StringListLogger(); ... ; logger.LoggedLines.ShouldContain(x=>x.Matches("kilroy was here")

TestBase.FakeDb

Works with Ado.Net and technologies on top of it, including Dapper.

* fakeDbConnection.SetupForQuery(IEnumerable<TFakeData>; )
* fakeDbConnection.SetupForQuery(IEnumerable<Tuple<TFakeDataForTable1,TFakeDataForTable2>> )
* fakeDbConnection.SetupForQuery(fakeData, new[] {""FieldName1"", FieldName2""})
* fakeDbConnection.SetupForExecuteNonQuery(rowsAffected)
* fakeDbConnection.ShouldHaveUpdated(""tableName"", [Optional] fieldList, whereClauseField)
* fakeDbConnection.ShouldHaveSelected(""tableName"", [Optional] fieldList, whereClauseField)
* fakeDbConnection.ShouldHaveUpdated(""tableName"", [Optional] fieldList, whereClauseField)
* fakeDbConnection.ShouldHaveDeleted(""tableName"", whereClauseField)
* fakeDbConnection.ShouldHaveInvoked(cmd => predicate(cmd))
* fakeDbConnection.ShouldHaveXXX().ShouldHaveParameter(""name"", value)
* fakeDbConnection.Verify(x=>x.CommandText.Matches(""Insert [case] .*"") && x.Parameters[""id""].Value==1)

TestBase.Mvc

ControllerUnderTest.Action()
  .ShouldbeViewResult()
  .ShouldHaveModel<TModel>()
  .ShouldEqualByValue(expected)
ControllerUnderTest.Action()
  .ShouldBeRedirectToRouteResult()
  .ShouldHaveRouteValue(""expectedKey"", [Optional] ""expectedValue"");

ShouldHaveViewDataContaining(), ShouldBeJsonResult() etc.

TestBase.Mvc Version 4 for netstandard20 & AspNetCore Mvc

Test your controllers using by specifying your MVCApplications Startup class:

[TestFixture]
public class WhenTestingControllersUsingAspNetCoreTestTestServer : HostedMvcTestFixtureBase
{
    [TestCase(""/dummy/action?id={id}"")]
    public async Task Get_Should_ReturnActionResult(string url)
    {
        var id=Guid.NewGuid();
        var httpClient=GivenClientForRunningServer<Startup>();
        GivenRequestHeaders(httpClient, ""CustomHeader"", ""HeaderValue1"");
            
        var result= await httpClient.GetAsync(url.Formatz(new {id}));

        result
            .ShouldBe_200Ok()
            .Content.ReadAsStringAsync().Result
            .ShouldBe(""Content"");
    }

    [TestCase(""/dummy"")]
    public async Task Put_Should_ReturnA(string url)
    {
        var something= new Fixture().Create<Something>();
        var jsonBody= new StringContent(something.ToJSon(), Encoding.UTF8, ""application/json"");
        var httpClient=GivenClientForRunningServer<Startup>();
        GivenRequestHeaders(httpClient, ""CustomHeader"", ""HeaderValue1"");

        var result = await httpClient.PutAsync(url, jsonBody);

        result.ShouldBe_202Accepted();
        DummyController.Putted.ShouldEqualByValue( something );
    }
}

TestBase.Mvc Version 3 for Net4

Use the Controller.WithHttpContextAndRoutes() extension methods to fake the http request & context. By injecting the RegisterRoutes method of your MvcApplication, you can use and test Controller.Url with your application's configured routes.

ControllerUnderTest
  .WithHttpContextAndRoutes(
    [Optional] Action<RouteCollection> mvcApplicationRoutesRegistration, 
    [optional] string requestUrl,
    [Optional] string query = """",
    [Optional] string appVirtualPath = ""/"",
    [Optional] HttpApplication applicationInstance)

ApiControllerUnderTest.WithWebApiHttpContext<T>(
    HttpMethod httpMethod, 
    [Optional] string requestUri,
    [Optional] string routeTemplate)

Can be used in both NUnit & MS UnitTestFramework test projects.

• Building on Mono : define compile symbol NoMSTest to remove dependency on Microsoft.VisualStudio.QualityTools.UnitTestFramework

ChangeLog

4.0.5.1 TestBase.Mvc partially ported to AspNetcore 4.0.4.0 StreamShoulds 4.0.3.0 StringListLogger as MS Logger and as Serilogger 4.0.1.0 Port to NetCore 3.0.3.0 Improves FakeDb setup 3.0.x.0 adds and/or corrects missing Shoulds() 2.0.5.0 adds some intellisense and FakeDbConnection.Verify(..., message,args) overload