Comments on: Best Practices, Mock Usage Pattern http://www.elilopian.com/2007/04/26/best-practices-mock-usage-pattern/ Creating better software Mon, 02 Jan 2012 09:09:26 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Eli Lopian http://www.elilopian.com/2007/04/26/best-practices-mock-usage-pattern/comment-page-1/#comment-792 Eli Lopian Sun, 29 Apr 2007 21:46:59 +0000 http://www.elilopian.com/2007/04/26/best-practices-mock-usage-pattern/#comment-792 Ian, There are a few reasons to put Verify in the test method: 1. In those cases where the test throws some kind of exception. The TearDown will run a Verify and you will see many failures that will make it harder to find the real problem. 2. Since NUnit 2.2, all failures in the TearDown are ugly, with big call stacks making it harder to understand. Note: There is no reason to call ClearAll right after Verify, because Verify clears all the mocks too. The reason that ClearAll is called in the TearDown are for those cases where the tests throws an exception. Ian,
There are a few reasons to put Verify in the test method:
1. In those cases where the test throws some kind of exception. The TearDown will run a Verify and you will see many failures that will make it harder to find the real problem.
2. Since NUnit 2.2, all failures in the TearDown are ugly, with big call stacks making it harder to understand.

Note: There is no reason to call ClearAll right after Verify, because Verify clears all the mocks too. The reason that ClearAll is called in the TearDown are for those cases where the tests throws an exception.

]]> By: Ian Davis http://www.elilopian.com/2007/04/26/best-practices-mock-usage-pattern/comment-page-1/#comment-711 Ian Davis Thu, 26 Apr 2007 11:04:03 +0000 http://www.elilopian.com/2007/04/26/best-practices-mock-usage-pattern/#comment-711 Is there any particular reason that you are calling Verify() in the test? I have defaulted (perhaps wrongly) to putting all of my mock management calls into the SetUp and TearDown methods. If a test is run that does not use mocking then I am out a small bit of performance, but it is handy. It also allows me to refactor my tests more easily. Below is what I try to start with when testing a class with mocks. <code> [TestFixture] public class MyTests { #region Setup/tear down [TestFixtureSetUp] public void InitTestFixture() { } [TestFixtureTearDown] public void CleanUpTestFixture() { } [SetUp] public void InitTest() { MockManager.Init(); } [TearDown] public void CleanUpTest() { MockManager.Verify(); MockManager.ClearAll(); } #endregion } </code> Is there any particular reason that you are calling Verify() in the test? I have defaulted (perhaps wrongly) to putting all of my mock management calls into the SetUp and TearDown methods. If a test is run that does not use mocking then I am out a small bit of performance, but it is handy. It also allows me to refactor my tests more easily. Below is what I try to start with when testing a class with mocks.


[TestFixture]
public class MyTests {
#region Setup/tear down

[TestFixtureSetUp]
public void InitTestFixture() {
}

[TestFixtureTearDown]
public void CleanUpTestFixture() {
}

[SetUp]
public void InitTest() {
MockManager.Init();
}

[TearDown]
public void CleanUpTest() {
MockManager.Verify();
MockManager.ClearAll();
}

#endregion
}

]]>