Quality Code book, authored by Stephen Vance, covers the different aspects of software development lifecycle with focus on delivering quality product. In the book, Stephen discusses the practices for supporting software craftsmanship testing. InfoQ spoke with the author about the book and the best practices for testing application code.
Hadoop MapReduce jobs have a unique code architecture that raises interesting issues for test-driven development. In this article Michael Spicuzza provides a real-world example using MRUnit, Mockito, and PowerMock to solve these problems.
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
Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project. 5
Testing is a major activity in any development lifecycle. If we want to effectively use it, the ease of testing should be addressed from the early stages of building the system. 5
InfoQ have talked to Dan North, Gojko Adzic, Elizabeth Keogh and Matt Wynne about Specification by Example, Executable Specifications and Feature Injection and how they relate to BDD. 1