Home » Archives

Content tagged with: rhino

[19 Aug 2010 | No Comment | ]

The buzz is on, everyone is talking about those NoSQL databases, but what ARE they? Do I really need to SQL behind? In this session, we will explore key / value databases, document databases, graph databases and column family databases. Their strong and weak points, and when you should use them. We will also discuss the options available for the .NET community on the NoSQL. In particular, we will look at Rhino DHT and Raven DB, two NoSQL databases on the .NET platform.
http://skillsmatter.com/podcast/open-source-dot-net/nosql-on-dot-net

[5 Oct 2009 | No Comment | ]

In this episode we are going to continue our series on learning how to use an isolation framework (Rhino Mocks) to help create simpler and more reliable unit tests. This time around we are going to be focusing how to use Partial Mocks to test abstract classes and methods within a concrete class.
http://www.dimecasts.net/Content/WatchEpisode/142

[7 Sep 2009 | No Comment | ]

In this episode we are going to continue our series on learning how to use an isolation framework (Rhino Mocks) to help create simpler and more reliable unit tests. We are going to focusing this episode on how to setup you mocks when you need to mock a class with either Out or Ref arguments.
http://www.dimecasts.net/Content/WatchEpisode/138

[28 Aug 2009 | One Comment | ]

Beyond the simplest scenarios, all objects had collaborators that they work with. This flies in the face of testing objects in isolation. This is the problem that mock objects were created to solve. In this talk you will learn what mock objects are, how to utilize them and best practices on when / how to utilize them. Rhino Mocks is a mock objects framework for .Net whose core goals are to let the developer rely on the compiler work well with refactoring tools.

[21 Jul 2009 | No Comment | ]

In this episode we are going to continue our series on learning how to use an isolation framework (Rhino Mocks) to help create simpler and more reliable unit tests. We will focus our learning this time around on the various ways you can setup and validate expectations on your stubs/fakes. Validating these expectations will allow your to confirm in tests your dependencies are being used in the manor expected.
http://www.dimecasts.net/Content/WatchEpisode/127
Resources
Rhino Mocks Home Page
Episode Source Code