testing ASP.net MVC 3 business/data logic

Question

What is the best way to test data access layers and business logic in mvc 3 solutions?

I currently have a project where I am using repository classes to access databases, which in turn use hibernate. When I try to create a unit test for them in the auto generated unit tests, they always fail since the configuration for nhibernate is in web.config and and it doesnt try to look there. What am i doing wrong? This particular method returns this error

"The Web request 'http://localhost:35601/' completed 
successfully without running the test"

The test methods look like this

    [TestMethod()]
    [HostType("ASP.NET")]
    [AspNetDevelopmentServerHost("C:\\Users\\...", "/")]
    [UrlToTest("http://localhost:35601/")]
    public void GetByIdTest()
    {
        string someid= "..";
        SomeObj actual = MyRepository.GetById(someid);
        Assert.AreEqual(some, SomeObj.id);
    }

How do i get this to work properly?

Is the unit test above in the same project as your MVC application? If so (or not) could you place the configuration is an app.config? I usually put tests in a second project and use an app.config file, that may or may not be an option based on where the unit test is. — marteljn
– marteljn, Commented May 20, 2012 at 3:19
@marteljn Putting the settings in app.config helped but I have run into another issue. The MVC solution gets the hibernate session from a static session factory class that keeps track of hibbernateSession per asp.net session. When running the test, the session is basically null. This can be taken care with dependency injection but is there another simpler way without having to change my regular code? — randomThought
– randomThought, Commented May 20, 2012 at 5:36

Community · Accepted Answer · 2017-05-23 10:09:06Z

1

Putting the settings in the app.config should solve the issue you posed above however, the more correct answer is that you should be using a mocking framework to mock the nHibernate session.

The fact that you found an area that you would need to change to accomodate testing is great!!! That is one advantage of unit testing; you find coupling in your code that should be refactored.

I found another post that addresses what you are trying to do directly Mocking an NHibernate ISession with Moq. There are two answers in the post that offer to approaches which may be helpful.

I hope this helps. I havent used nHibernate so I can't speak authoritatively about it or that the link above will provide you with an answer, but each answer has ten upvotes so it looks like it was a solid post!

edited May 23, 2017 at 10:09

CommunityBot

11 silver badge

answered May 20, 2012 at 16:27

marteljn

6,5263 gold badges32 silver badges44 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

testing ASP.net MVC 3 business/data logic

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related