Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

.NET Class Mocking Requires an Interface: A Code Smell? More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Been There. Done That. (Score:1)

by jk2addict (4946)

That's the one thing I hate about writing NUnit tests...not being able to Mock when I need to without it turning into a science fair project.

The later verison of TypeMock.NET do allow you to mock classed without interfaces. Last I checked, it still had a problem with mocking a superclass of a current class, or maybe that's a superclass that is in unmanaged code.

Either way, much harder than in Perl TDD...and I sure do miss local() sometimes too.
- Re:Been There. Done That. (Score:1)
  
  by Mark Leighton Fisher (4252) on 2007.07.06 11:40 (#56020) Homepage Journal
  
  I like that – mocking a .NET class as a science fair project. That kind of annoyance is what prompted the essay, as I think the .NET team just didn't think through all the implications of their design.
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.