Development Central
Stubbing problems with Rhino Mocks
09/04/08
Stubbing problems with Rhino Mocks
I’ve been doing a fair amount with Rhino Mocks lately, and found that it doesn’t support one common scenario well.
You have an interface with several read-only properties (get accessors but no set accessors). You want to stub that interface.
It appears that you have to actually create a MockRepository rather than just using the static method to create the stub. You then have to call SetupResult.For on the properties, and put the repository instance into replay mode. Worse, you then can’t change the results (as far as I can tell). This makes it more difficult to define setup fixtures and the like.
I’m hoping Rhino Mocks v3.5 will resolve this issue. If it doesn’t, I may be looking for a new mocking framework.
Update - September 7, 2008
Please see Ayende’s comment.
Comments, Pingbacks:
· http://www.ayende.com/Blog/ If you want to change values after calls, you need to use Expect.Call()
Permalink
09/05/08 @ 04:55 Leave a comment:
Development Central
Development Central is the blog of Bill Sorensen, a professional software developer. Much of this will relate to C#, .NET, and OOP in general.
Disclaimer
These postings are provided "AS IS" with no warranties and confer no rights.
Search
Categories
- All
- .NET (44)
- Agile (21)
- Announcements [A] (9)
- Books (28)
- C# (25)
- Continuous Integration (15)
- Conventions (13)
- IoC (10)
- Persistence (4)
- PowerShell (6)
- Quality (30)
- ReSharper (8)
- Security (6)
- SQL (8)
- Testing (30)
- TFS (7)
- Tips (49)
- Tools (56)
- Web (12)
- Windows (26)
- WTF (6)
Archives
- June 2010 (1)
- May 2010 (2)
- April 2010 (2)
- March 2010 (2)
- February 2010 (1)
- January 2010 (2)
- December 2009 (2)
- November 2009 (4)
- October 2009 (5)
- September 2009 (3)
- August 2009 (7)
- July 2009 (4)
- More...
Choose skin
Misc
XML Feeds
What is RSS?
Who's Online?
- Guest Users: 5
