The role of QA is changing. In the waterfall world, QA teams, siloed away from developers, are slow and costly. Unit testing passes the responsibility for software quality to the developers and leads to better code, reducing reliance on a separate QA department. Is unit testing a better way to ensure software quality – the ultimate goal of QA?
All the information, books and tools are out there, just pick up NUnit, and you’re good to go, right? Not exactly. Even before deciding to start unit testing, we need to sift through real experience of others; good and bad, horror stories and miracles (“This one test saved me a week of work!”). Then, we take the plunge, and realize: There’s so much to learn!
Automated Testing (unit/integration) is an integral part of any agile development process. However a project with significant logic housed in database code creates severe constraints to writing unit level tests, especially if it is large, complex and depend on data. We will explore the TST framework and a few ideas for writing and maintaining good tests for database code.
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
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