In the above 2-tier example, code is tightly coupled. There are various framework or test suite available to solve above problem ex: Rhino mocks, fakes etc.
Rhino mocks how to#
Now the question arises, how to solve the above problem? We have to do unit testing for our business logic layer not the data access layer.If something changes in database unit test will fail. Unit test is completely dependent on database(assume EmployeeDal accessing database).There are various disadvantages with the code written above Note: I will be using the same classes of data access layer and business logic layer through out this article and with some modification in the structure. We can use TestInitialize attribute for reusing the code.Īssert.AreEqual(employeeBal.GetEmployee(), " abc", " Return value is not equal") Though, Unit testing framework supports reusable code to some extent. In the unit test, one shouldn't worry about creating reusable code. So now the question, is it better to use common method?The answer is No. In the above methods, we are using identical code. In the above example, I used the precondition to verify whether the condition is true/false. Assert: Assert class is used to verify conditions in the unit tests using true/false precondition.TestMethod Attribute: used to identify test method.TestClass Attribute: used to identify classes that contains test methods.Thanks a bunch in advance.Var result = addTest.Add(value1, value2) Īssert.IsTrue(result = 14, " Result of the sum is working as expected") Īssert.IsFalse(result = 10, " Result of the sum is working not as expected") īefore going in depth, let's understand what are TestClass,TestMethod attributes and Assert. ProjectAddViewPresenter presenter = new ProjectAddViewPresenter(viewMock) ĭo you have any idea why is the exception? I am sorry for such long post but I can not resolve this. IEventRaiser raiser = LastCall.IgnoreArguments().GetEventRaiser() IProjectAddView viewMock = (IProjectAddView)mocks.CreateMock(typeof(IProjectAddView)) MockRepository mocks = new MockRepository() ProjectManager.CreateProject(_view.Project) Void OnProjectCreated(object sender, EventArgs args) _view.ProjectAdded += new EventHandler(OnProjectCreated) Throw new PresenterException("IProjectView can not be null.") Public ProjectAddViewPresenter(IProjectAddView view) > System.NullReferenceException : Object reference not set to an instance of an object. Running the test throws this "Error1TestCase 'AS.ProjectAddViewPresenterTests.AddNewProject'įailed: : Exception has been thrown by the target of an invocation.
Implementing the presenter is pretty straightforward. Test fails, which is good, since I haven’t yet implemented the I then ask the mockįramework to verify that all our expectations were met. Presenter which is the code being tested. So finally after setting all these expectations, I create an instance of Property, or event set on the mock instance is telling the mock that weĪre going to call that particular member. That we are done setting all our expectations and we are going toĪctually conduct the test now. What it really is doing, as far as I know, is telling the mock framework That line, the test would expect that null is attached to the loadįinally we call ReplayAll(). Worry about which method delegate gets attached to the event. Mocks will expect the that the Load event will be attached, but don’t To ignore the arguments in the last call. In the third line, I set an expectation that the The second line of code creates a dynamic proxy that implements the Public void VerifyAttachesToViewEvents ()
0 kommentar(er)
