C
Analyzed about 22 hours ago
This project aims to make interop between IronRuby objects and .NET objects easier. The idea is that it integrates nicely with bacon and later rspec and that it transparently lets you mock ironruby ojbects as well as CLR objects/interfaces. Caricature handles interfaces, interface inheritance, CLR
... [More]
objects, CLR object instances, Ruby classes and instances of Ruby classes.
From the start I wanted to do away with names like mock, stub, record, replay, verify etc. Instead I took the advice from Roy Osherhove and went with a name of Isolation for creating a mock.
An Isolation will create what in Rhino.Mocks would be called a DynamicMock (but can be a partial too) :) In Moq it would be the Loose mocking strategy.
The naming of the methods for creating mocks is the one that JP Boodhoo proposed [Less]