At the recent Agile Singapore conference Kevlin Henney gave two talks focusing on the importance of simplicity in architecture and implementation and on programming with Good Unit Tests (GUTS). He spoke to InfoQ about the thinking behind his talks and how they can be implemented.
In this important and thorough treatise “Integration Testing from the Trenches” Nicolas Frankel starts from basic definitions and develops the concepts of integration testing with a casual formalism that's intuitive and fun.
Quality Code book covers different aspects of SDLC with focus on delivering quality product. InfoQ spoke with author Stephen Vance about the book and best practices for testing applications.
To refactor legacy code, the ideal is to have a suite of unit tests to prevent regressions. However it's not always that easy. This article describes a methodology to safely refactor legacy code. 7
Hadoop MapReduce jobs have a unique code architecture that raises interesting issues for test-driven development. In this article Michael Spicuzza shows how to use MRUnit to solve these problems. 1
Many think that the role of testing is dead in agile, but I think it is growing and turning into better and effective testing; redefines the way things are done and the order in which they are done. 2
Waterfall QA teams are slow and costly. Siloed away from developers, is QA the best way to ensure software quality? Is unit testing a better way to ensure software quality? 11
Over the last few years unit testing has been considered a “solved problem.” All the information, books and tools are out there, just pick up NUnit, and you’re good to go, right? Not exactly. 1
We explore the TST framework and a few ideas for writing and maintaining good tests for database code. 2
In this article, Gil Zilberfeld cover tips on what to expect, and steps to take when starting out in order to make unit testing a part of development life. 11
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial. 13