Don’t Mock Yourself Out

Published January 18th, 2010 Under Software Testing | Leave a Comment

Ask experienced Rails developers what they think about mock objects and some will say “absolutely awesome” while others “absolutely horrible.” The problem with both of those answers lies their “absolute”-ness. Used appropriately, mock objects are a powerful design tool that can lead to highly maintainable applications. Used in the wrong context or for the wrong reasons, they can lead to painfully brittle test suites that do little to maintain confidence in an application. In this talk, David Chelimsky will explore mock objects in the abstract and in the context of Rails.

Testable Software

Published November 9th, 2009 Under Software Testing | Leave a Comment

In this talk David Evans and Mike Scott discuss the effect architectural decisions have on application testability. They assert that a testable architecture is inherently a better architecture, and demonstrate how testability in itself is an essential dimension in any architecture because of its relationship to good architectural patterns and practices.

http://skillsmatter.com/podcast/open-source-dot-net/testable-software

Isolation Frameworks: Learning to use Partial Mocks

Published October 5th, 2009 Under Unit Testing | Leave a 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

Isolation Frameworks: Mocking Out/Ref Arguments

Published September 7th, 2009 Under Unit Testing | Leave a 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

Interaction Based Testing with Rhino Mocks

Published August 28th, 2009 Under Unit Testing | Leave a 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.

PowerMock

Published August 24th, 2009 Under Unit Testing | Leave a Comment

PowerMock can be used to test code normally regarded as untestable! Have you ever heard anyone say that you should never use static or final methods in your code because it makes them impossible to test? Have you ever changed a method from private to protected for the sake of testability? What about avoiding “new”? Think again! PowerMock lets you mock static methods, remove static initializers, allow mocking without dependency injection and much much more. And it works just as well for J2EE as J2ME! This presentation will give the audience a good understanding on how to easily unit-test your code without the limitations of the common mock frameworks such as EasyMock and JMock.

Isolation Frameworks: Learning how to validate expectations

Published July 21st, 2009 Under Unit Testing | Leave a 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

« go back — keep looking »