Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am new to unit testing. I have a web application using asp.net mvc3 and s#arp lite. I want to add unit test to this application. so far, I have a test for each action in the controller class. Just curious, what else I need to test? Does view need to be tested too?
another question, all the testing example I found online are using moq or other tools to make fake data. Should we also test again the real database?
You should neither unit test views nor against a real database. Use unit tests for your code-level artifacts like controller actions, action filters, html helpers, models, anything written in C#.
For testing a real database and views, look to integration tests. Integration tests are not like unit tests, but you can still execute them using a unit test framework like nunit. Basically, you just write test code to drive a browser using something like Selenium WebDriver or Watin. But these are not really unit tests, they are integration tests, end-to-end tests, or user acceptance tests.