Comments on: TDD: Hand written stubs vs Framework generated stubs

By: miluch

miluch — Thu, 20 Jan 2011 18:38:47 +0000

Provided “We tried to keep on using the same stub instance of the dependency” you ended up using 2 references: hand rolled stub and framework mock.
I always try to make my test method self descriptive and try to avoid using setup methods. Following this, if i find that my test method become bloated with setup code i try to refactor it into seprate builder method/classes

By: TDD: Simplifying a test with a hand rolled stub at Mark Needham

TDD: Simplifying a test with a hand rolled stub at Mark Needham — Mon, 25 Jan 2010 21:24:43 +0000

[...] wrote a couple of weeks ago about my thoughts on hand written stubs vs framework generated stubs and I noticed an interesting situation where it helped me out while trying to simplify some test [...]

By: Bill Sorensen

Bill Sorensen — Fri, 22 Jan 2010 19:41:27 +0000

You could skip the Setup and fields and have a method that returns a controller (or a dependency, then create the controller in the test methods). Adjust as needed for your cases and add new methods as needed. Basically refactor your unit tests to remove duplication.

private Controller GetController(int dependencyResult)
{
ITheDependency theDependency = MockRepository.GenerateStub();
theDependency.Stub(t => t.SomeMethod()).Return(dependencyResult);

return new Controller(theDependency);
}

By: Giorgio Sironi

Giorgio Sironi — Tue, 19 Jan 2010 22:44:58 +0000

I think using generated Test Doubles is a symptom that abstractions are efficient, as their method’s behavior is forced to be simple. That said, often hand written stubs are more expressive.

By: Helltime for January 18 « I Built His Cage

Helltime for January 18 « I Built His Cage — Tue, 19 Jan 2010 04:03:27 +0000

[...] Mark Needham raps about framework-generated versus hand-written test stubs. The few times I used a tool to auto-generate anything about my unit tests was with Jtest, and the [...]

By: Tweets that mention TDD: Hand written stubs vs Framework generated stubs at Mark Needham -- Topsy.com

Sat, 16 Jan 2010 07:26:48 +0000

[...] This post was mentioned on Twitter by Mark Needham and planettw, Craig Taylor. Craig Taylor said: RT @markhneedham: handwritten vs framework generated stubs – some thoughts – http://bit.ly/4SxK3C [...]

By: David Ron

David Ron — Sat, 16 Jan 2010 00:38:21 +0000

I’m not familiar with Mockito, but I use jMock quite frequently. I often find myself writing:

@Test
public void testSomething(){
expectSomethingWillHappen()
service(findFromList(someList));
}

@Test
public void testSomethingElse(){
expectSomethingWillHappen()
service(findFromList(differentList));
}

private void expectSomethingWillHappen(){
IrrelevantObject dummyObject = new IrrelevantObjectBuilder.build();
context.checking(new Expectations(){{
one(dao).findobject(with(any(List.class)));
will(returnValue(dummyObject));
}});
}

This pattern works really really well, and is a lot more simple than hand-created mocks.

By: TDD: Thoughts on using a clock in tests at Mark Needham

TDD: Thoughts on using a clock in tests at Mark Needham — Fri, 15 Jan 2010 22:01:00 +0000

[...] wrote previously about my thoughts of where to use each of the two approaches and one example of where hand written stubs seems to make sense is the [...]