TableControllers Unit test

Question

So I'm trying to write a simple tablecontroller Unit test for my backend??

I havent been able to do so, all I've achieve is writing unit testing for ApiControllers but is there a way to write a Unit test for TableControllers?

What I'll like to do is this:

public class AuctionController : TableController
{
    protected override void Initialize(HttpControllerContext controllerContext)
    {
        base.Initialize(controllerContext);
        MobileServiceContext context = new MobileServiceContext();
        DomainManager = new EntityDomainManager(context, Request);
    }

    // GET tables/Auction
    public IQueryable GetAllAuction()
    {
        return Query(); 
    }

    // GET tables/Auction/48D68C86-6EA6-4C25-AA33-223FC9A27959
    public SingleResult GetAuction(string id)
    {
        return Lookup(id);
    }

    // PATCH tables/Auction/48D68C86-6EA6-4C25-AA33-223FC9A27959
    public Task PatchAuction(string id, Delta patch)
    {
        return UpdateAsync(id, patch);
    }

    // POST tables/Auction
    public async Task PostAuction(Auction item)
    {
        Auction current = await InsertAsync(item);
        return CreatedAtRoute("Tables", new { id = current.Id }, current);
    }

    // DELETE tables/Auction/48D68C86-6EA6-4C25-AA33-223FC9A27959
    public Task DeleteAuction(string id)
    {
        return DeleteAsync(id);
    }
}

and i wish to make a test controller like this one:

[TestClass]
public class AuctionControllerTests
{
    private readonly AuctionController _controller;

    public AuctionControllerTests()
    {
        _controller = new AuctionController();
    }

    [TestMethod]
    public void Fetch_all_existing_items()
    {
        Assert.Equal(2, _controller.GetAllTodoItems().ToList().Count);
    }
}

how can I possibly be able to get this to work??? Please I would appreciate your help a lot.

Enrique A. Pinelo Novelo · Accepted Answer

So Thanks for the mocking solution, It worked but I wrote a generic better solution without using mocking framework, I'll apply mocking framework later, right now I'll stick with fakes and real dbs for integration tests.

but firstable I wrote a Generic TableController in order to apply multiple EntityData and DbContext for those who had more than one Context, also you could apply a FakeContext thanks to the abstraction of interfaces but i havent applied to this example.

First This is my BaseController:

//This is an abstract class so we can apply inheritance to scalfolded tablecontrollers.
public abstract class BaseController : TableController where TModel : class, ITableData
                                                                                       where TDbContext:DbContext, new()
{
    protected override void Initialize(HttpControllerContext controllerContext)
    {
        base.Initialize(controllerContext);
        var context = new TDbContext();
        SetDomainManager(new EntityDomainManager(context, Request));
    }

    public void SetDomainManager(EntityDomainManager domainManager)
    {
        DomainManager = domainManager;
    }
}

this is my scalfolded controller with my basecontroller applied!!!

public class AuctionController : BaseController    
{        
    public IQueryable GetAllAuction()
    {
        return Query(); 
    }

    // GET tables/Auction/48D68C86-6EA6-4C25-AA33-223FC9A27959
    public SingleResult GetAuction(string id)
    {
        return Lookup(id);
    }

    // PATCH tables/Auction/48D68C86-6EA6-4C25-AA33-223FC9A27959
    public Task PatchAuction(string id, Delta patch)
    {
         return UpdateAsync(id, patch);
    }

    // POST tables/Auction
    public async Task PostAuction(Auction item)
    {
        Auction current = await InsertAsync(item);
        return CreatedAtRoute("Tables", new { id = current.Id }, current);
    }

    // DELETE tables/Auction/48D68C86-6EA6-4C25-AA33-223FC9A27959
    public Task DeleteAuction(string id)
    {
         return DeleteAsync(id);
    }
}

With my generic application I can apply any DbContext that way you could even apply FakeDbContexts in order to avoid SqlConnection or Cloud connection such as Azure which is the one I used in this example.

UPDATED MARCH 14th, 2018

All this two library are on my Backend project, now I'll show you my test project in order to Unit Test a TableController

 public abstract class ControllerTestBase where TController : BaseController, new() 
                                                                           where TModel : class, ITableData
                                                                           where TDbContext: DbContext, new()
{
    protected readonly TController Controller;

    protected ControllerTestBase()
    {   
        Controller = new TController();
        Controller.Configuration = new HttpConfiguration();
        Controller.Request = new HttpRequestMessage();
        var context = new TDbContext();        
        Controller.SetDomainManager(new EntityDomainManager(context, Controller.Request));
    }
}

Ok thanks to this abstract class you can supress the initialize setup from the testing library because each time you run a test it will call the generic test constructor, setting up all the necessary requierements and thus avoid ArgumentNullExceptions and InvalidOperationExceptions such common problem for unit testing tablecontroller since isnt quite intuitive to initialize as an ApiController.

Finally if you modify this then you can run a test like this:

[TestClass]
public class AuctionControllerTest : ControllerTestBase
{
    [TestMethod]
    public void Fetch_All_Existing_Items()
    {
        Assert.AreEqual(1, Controller.GetAllAuction().ToList().Count);
    }
}

thanks to my generic application you can now use this code as an example to be apply to your TableControllers and also if you follow the Interface Segregation Principle you could apply FakeDbContext to your Controllers.

For those who helped me thanks you opened my mind into coming with this solution!!!

TableControllers Unit test

Answers (2)

Related Questions