Top 10 Mistakes in Unit Testing
Published September 6th, 2010 Under Unit Testing | 2 Comments
In this session we review the top 10 ways you can cause unit testing to fail to work for your project. From readability problems and lack of trust to mock object abuse and semi-integration testing – these gotchas can save you lots of time, sweat, and tears on your current and next projects.
Download video in other formats and slides
The State of the Art on .NET
Published August 4th, 2010 Under Unit Testing | Leave a Comment
Amanda Laucher and Josh Graham present at an introductory level some of the most important elements of the .NET ecosystem: F#, M, Boo, NUnit, RhinoMocks, Moq, NHibernate, Castle, Windsor, NVelocity, Guerilla WCF, Azure, MEF.
http://www.infoq.com/presentations/The-State-of-the-Art-on-.NET
Moles: Mocking the Un-Mockable
Published April 26th, 2010 Under Unit Testing | Leave a Comment
In this episode we are going to take at how to use Pex and Moles for .Net. Unit testing is great, but most free isolation frameworks require that your mocks implement an interface. But what do you do when the class you are trying to mock is static or sealed with no interface. If you can’t modify the class then your unit testing efforts are usually stuck. Moles, the new free isolation framework from Microsoft, supports mocking almost any CLR based class (including sealed and static classes).
http://www.dimecasts.net/Content/WatchEpisode/170
Learning how to use Manual Mocks for Testing
Published March 1st, 2010 Under Software Testing, Unit Testing | Leave a Comment
In this episode we are going to take a look at how to use manual mocks for testing. Often times when creating unit tests we need to work in isolation in order to cover the paths we are attempting to test. When we want to test in isolation you can use a testing technique where you mock out your dependencies. When using Mocks you can either do it manually (what we are looking at) or you can use a mocking framework like Rhino Mocks. Either way you achieve the same results.
http://www.dimecasts.net/Content/WatchEpisode/164
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.
keep looking »