Vagif Abilov's blog on .NET

Browse by Tags

All Tags » unit testing (RSS)
NUnitForVS: integrating NUnit tests into Visual Studio
Roy Osherove listed advantages of NUnit over MsTest but also mentioned one MsTest’s strength that can be crucial for many developers: “the integration with other team system tools and reporting is just beyond compare and the reporting alone helps alot...
When NUnit stops working on a build machine…
… then it’s time to check the registry entries. Make sure you see something like this: In case the build runs in the context of a dedicated user, not the one who logs on to a build machine and install applications, then it is likely that the build user...
.NET mocking framework comparison
A couple of good sources for those who need to decide: Capability comparison made by Morgan Soley. Half year old but with a feature comparison table. Recently updated comparison by Andrew Kazyrevich. TypeMock Isolator is a clear winner if it fits in your...
We Can Mock It Out
Today there was a first day of Norwegian Developers Conference . Great speakers and great sessions. I attended talks by Scott Hanselman, Luca Bologneze, Jeremy Miller, Udi Dahan and Juval Lowy. But that was not all! After hours TypeMock guys arranged...
True unit tests and cross-domain calls
In our company we recently started marking automated tests as “Unit” and “Integration” for the purpose of running unit tests frequently (and on every check-in). Such separation obviously requires clear definition of what is a unit...
TypeMock Isolator and matching faked method’s arguments – part 3
Part 1 Part 2 I promised to address matching reference and output arguments using lambda-based syntax that I proposed for TypeMock Isolator. Before getting there I would like to retract my original comment that faked method’s arguments should be matched...
TypeMock Isolator and matching faked method’s arguments – part 2
I was glad to see that my thoughts about figuring out the best syntax to control the match of faked method’s arguments haven’t been unnoticed by TypeMockians. Eli Lopian raised a few questions, and addressing them seems to be crucial for materialization...
How I would match faked method's arguments if I was TypeMock Isolator
I enjoy compactness and clarity of TypeMock Isolator AAA syntax. But it still lacks certain features in comparison with the original RecordExpectation-based syntax. One of such features is support for exact match of method's attributes. Here's...