A common theme amongst people professing “best practices” for unit tests is that you should only write a single assertion for each test. People who make these proclamations rarely show any unit test and those that do only show one. Yet this pattern may require a dozen other unit tests to ensure quality for even a trivial operation. This article uses examples to question that recommendation.
Rajneesh Namta shares the lessons he’s learned while automating software tests on a recent Agile project. The techniques he recommends illustrate how the Agile principles we follow when building software apply equally as well to building an automated regression test suite: start small, build iteratively and incrementally, prioritize, focus on value, work transparently, respond quickly to change.
Testing is a major activity in any development lifecycle - a large part of a project budget is spent on it. If we want to effectively use it, the ease of testing should be addressed from the early stages of building the system.
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
Liam O'Connor explains some of the misconceptions about testing with the hope that it will help you and your team to decide when it is appropriate to test, and when it isn't. 17
This is the third and final part of the late Jamie Phillip’s exploration into the world of coding kata’s and Behavior Driven Design. 1
In part 2 Jamie Phillips introduces behavior driven development and explains how it can improve the effectiveness of unit testing. 1
Regardless of experience there are always opportunities to strengthen one’s skills. Jamie Phillips demonstrates how he used coding katas to improve upon his skills after 8 years of writing C# code. 2
The skills needed to be hyper-productive in an agile project differ from those required by a traditional one. This article identifies behavioral and technical skills required to give a team that edge. 16
Outside of a certain Agile sweet-spot, there are more barriers and costs to applying Agile techniques. None of these obstacles prevents Agile in itself but each increases the cost of getting to Agile. 4
TekPub is an interesting case about company who started on ASP.NET MVC and quickly moved to Ruby on Rails. We had the opportunity to talk with them about their technology turnaround. 21