The 2nd Annual Google Test Automation Conference (GTAC) in New York on August 23 and 24, 2007. In the world of developer-facing automated tests, IBT is arguably one of the most controversial topics. One side claims that “pure” unit testing is a way to ensure that code behaves as specified, providing design and maintenance benefits as well. Another group claims that IBT is a great way to generate code bloat and test things that do not need to be tested. Matt and Sean will try to go beyond the clichés and hype of “Mock Always” verses “Mock Never.” Instead, they’ll strive to find the appropriate places to use IBT, and pass on some tools to help you with your ultimate decision. Along the way, they will cover some common mistakes, anti-patterns, and things to consider.

Related Posts:

• PowerMock
• Grails eXchange 2007: Unit Testing and Mock Objects with Groovy