Facebook Twitter
Yet Another Lambda Blog » Code testing in Haskell Yet Another Lambda Blog » Code testing in Haskell A few weeks ago I wrote that for 3 years I used Matlab as my main programming language. Before that however I was developing in Java. While Java can be criticized for its design – and I noticed that some Haskallers look down on it – it learned me one very important thing: code testing. Java’s JUnit was very important in popularizing Test Driven Development (TDD) and code testing in general.
Rhino Mocks 3.5 introduces some new concepts, mostly by building upon the language features of C# 3.0. Users on the 2.0 platform need not worry, there are enough goodies for them as well (inline constraints, for example), but the focus of this document is on the use of Rhino Mocks with C# 3.0. Edit New things in Rhino Mocks 3.5:Arrange, Act, Assert modelLambda and C# 3.0 extensionsInline constraintsProperty Setters Explicit Expectation APISupport for mocking interface in C++ that mix native and managed types.Allow a mock object to return to record mode without losing its expectationsCreateMock was deprecated in favor of StrictMockBetter error handling in edge cases.Fixed an issue with mocking internal classes and interfacesNew event raising syntaxEdit In general, I recommend following the principle of "Test only one thing per test". Applying this to Rhino Mocks (and mocking in general), each unit test should validate no more than one significant interaction with another object. Rhino Mocks 3.5 - Ayende @ Wiki Rhino Mocks 3.5 - Ayende @ Wiki
Rhino Mocks is the most popular Mock Object Framework for .NET. The purpose of this blog entry is to provide a brief introduction to Rhino Mocks. In particular, I want to describe how you can use Rhino Mocks when building ASP.NET MVC web applications. TDD : Introduction to Rhino Mocks TDD : Introduction to Rhino Mocks
MoQ now uses xUnit for its unit tests After talking to a few guys during the MVP summit and the proceedings of the ALT.NET conference, I decided to give xUnit a serious try. I’m quite pleased with it. Using .NET idioms rather than excessive attributes (i.e. [SetUp] vs class constructor, [TearDown] vs IDisposable, etc.) is a good thing. MoQ now uses xUnit for its unit tests
xUnit.net Contrib CodePlexProject Hosting for Open Source Software xUnit.net Contrib xunitcontrib Downloads and installation notes: On this page:What is it? xUnit.net Contrib
xUnit.net - Unit testing framework for C# and .NET (a successor to NUnit)
Download Download Current Stable Release: NUnit 2.6.3 Under Development: NUnit 2.9.6 Download Types The following types of downloads are provided: