07 Jul '13, 5pm

Geek glossary: mock via @pivotallabs

This is my second post on the trinity of test tools known as ‘test doubles’. The first covered stubs. This one is all about mocks, which are woefully misunderstood and loathed by many. If you want to know more about the history of mock objects, get a copy of GOOS . It’s my favourite recent work on TDD and software design, and it’s written by folks involved in the invention of mocks. Unlike my previous post, I’m going to concentrate on pure mock objects. The disadvantages of partial mocks are similar to those of partial stubs. First, a definition: a mock is an object that expects messages, and consequently verifies the outputs of the system under test. Why mock? Mocks were originally designed to avoid the ‘traditional’ TDD practice of adding code to an object purely for state verification. Their use as a design tool is worth getting to grips with, even if you don’t intend t...

Full article: http://pivotallabs.com/geek-glossary-mock/


Geek glossary: stub via @pivotallabs

pivotallabs.com 06 Jul '13, 9pm

Over the next few blog posts I intend to bang a few more nails in the coffin of the widespread misunderstanding of stubs, ...

Learning Processes via @pivotallabs

pivotallabs.com 07 Jul '13, 7am

Every person have their own way of learning, for each one of us there is a method that works better. We have to try and un...

We’ve found the awesome singularity

We’ve found the awesome singularity

hackaday.com 09 Jul '13, 3pm

We’ve found the awesome singularity July 9, 2013 By Brian Benchoff 19 Comments Yes, that’s exactly what you think it is. A...