Doug Hiebert discusses the principles and objectives behind automated testing, TDD, Unit and Integration Testing, using asserting and mocking to write tests, and static analysis.
Aaron Bedra shows code samples for writing Clojure tests using the test.generative framework, explaining why this framework and testing are useful.
Jay Harris offers tips on using unit testing to improve the performance of applications.
David Starr demoes Pex –a parameterized white box unit test tool- and Moles –an isolation framework-, two .NET tools useful for test-first development.
Scott Allen explains how to create unit tests for applications making use of the ADO.NET Entity Framework 4.1.
Ulf Wiger discusses the importance of automated testing along with some lessons learned at Ericsson, including using randomized and extensive testing, aiming to achieve system robustness.
Roy Osherove discusses the difficulties met when trying to test code embedded in a framework (cog), presenting several possible solutions to create unit tests for cogs. He also presents Excavation, a technique used to create a domain specific test framework and some patterns used for cog isolation. The discussion centers around Silverlight code examples.
John Hughes shows how to explore the possible bugs of a code by creating a series of tests in Erlang and using multiple test frameworks, discovering the faults through successive tests and evaluating the frameworks while doing it.
Automation is essential to DevOps. The infrastructure as code concept drives many of today’s cutting edge automaton techniques. What is it all about? Where are its limitations?
In this presentation recorded at QCon SF 2008, Jeff Brown presents Gallio, a test automation platform, and MbUnit, a test automation framework for .NET. He shows how a test framework works on Gallio and talks about the difficulties faced when building such a platform.
We're charged with the task of writing software that is reliable, sturdy, and trustworthy. We could all write tests and extensive preconditions for our code, and choose languages which make errors less likely, but across the industry we don't do any of these things uniformly. Michael Feathers looks at error-prevention in the short history of our discipline and considers our possible futures.