A New Trick
I have read this post Interaction based testing using TypeMock.
This code:
Mock clientMock = MockManager.Mock(typeof (Client)); clientMock.Strict = true; Client client = new Client();
Is exactly the same as this code:
MockObject<Client> clientMock = MockManager.MockObject<Client>(); Client client = clientMock.Object;
I prefer the latter, the main reason being that using MockObject ensures that the Object is the one being mocked.
Here is an example that won’t work because we added a new Mock before the previous code:
Mock firstClientMock = MockManager.Mock(typeof (Client)); Mock clientMock = MockManager.Mock(typeof (Client)); clientMock.Strict = true; Client client = new Client(); // this will be contolled by firstClientMock
In this case our client is controlled by the firstClientMock instead of the clientMock. This won’t happen if we use MockObject
Recent Posts
- Top 5 questions to ask when checking references
- Unacceptable: Unit testing will take 20 years to catch on
- The 4 reasons why we DIDN’T choose Oslo
- Typemock Academy Launch
- The First Rule to Software Craftsmanship
Categories
- .NET Tests
- Agile
- Code Integrity
- Community
- Debugging
- Fun
- Management for Geeks
- Marketing
- Product
- Release
- Reviews
- SharePoint
- TDD
- Time Management
- Uncategorized
- Unit Tests
Archives
- August 2010
- May 2010
- April 2010
- March 2010
- February 2010
- December 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- December 2008
- November 2008
- August 2008
- July 2008
- May 2008
- April 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
