Archives for the 'Reviews' Category
Typemock and Design Issues
The new field mock feature that enables developers to mock fields has raised the questions:
Who needs to mock fields, (only bad programmers)?
Does Typemock advocate bad design?
Is Typemock too powerful?
Advocating Good Design
Well, lets get one thing straight. I do advocate good design, the design of the software is an important factor and one that I spend a […]
Debugging Mocked Methods
Although strict XP practices, value tests more then debugging, there are many cases where you still have to debug the code base to find defects. Doing this with mocked objects can be very fishy.
Evaluating Mocked Properties
When evaluating methods and Properties in the Debugger, the Debugger Hi-Jacks the running application to run the code that evaluate […]
The Ultimate Proof for TypeMock
When developer using TypeMock find it an indispensable tool, it is a sign that we really help ease the task of building lasting software.
Karell says it better:
The best way to see if you need something is to stop using it (or be prevented from using it) for a while and see if you reach out for it […]
Interview on DotNetRocks
Richard has invited me for a chat on DotNetRocks. The topic being Unit Testing and Dependency Injection. I still have to find a nice photo for the show. Stay tuned
Bookmark at:
MailFrame’s CodeSpell
I had quite an embarrassing moment when Scott Hanselman who is reviewing TypeMock.NET sent me his first impressions.
The e-mails where screen-shots of spelling typo’s in TypeMock’s API’s documentation. It turns out that there are quite a few spelling mistakes in the API’s documentation.
Well, we added a task to fix all these, but […]
Subscribe!
RSS 2.0