Introduce deep stubs to help dealing with legacy code

[GoogleCodeExporter]

Use it only for legacy code! Be aware of LoD and write simple & easily
testable code! Whenever mock returns a mock, a fairy dies!

Foo mock = mock(Foo.class, RETURNS_DEEP_STUBS);

// note that we're stubbing a chain of methods here: getBar().getName()
when(mock.getBar().getName()).thenReturn("deep");

// note that we're chaining method calls: getBar().getName()
assertEquals("deep", mock.getBar().getName());

Original issue reported on code.google.com by szcze...@gmail.com on 14 Feb 2010 at 9:25

[GoogleCodeExporter]

Thanks James for the patch!

Original comment by szcze...@gmail.com on 14 Feb 2010 at 9:25

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This issue was closed by revision r1851.

Original comment by szcze...@gmail.com on 14 Feb 2010 at 9:27

• Changed state: Fixed

[GoogleCodeExporter]

Issue 149 has been merged into this issue.

Original comment by szcze...@gmail.com on 28 Feb 2010 at 9:03

[GoogleCodeExporter]

Original comment by szcze...@gmail.com on 28 Feb 2010 at 9:04

• Added labels: Milestone-Release1.8.3

[GoogleCodeExporter]

Original comment by szcze...@gmail.com on 28 Feb 2010 at 9:05

• Changed title: Introduce deep stubs to help dealing with legacy code