BT
Older rss

Quality Code - Book Review and Interview

Posted by Srini Penchikala on  Feb 25, 2014

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.

Refactoring Legacy Applications: A Case Study

Posted by Chen Ping on  Feb 27, 2013

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

Unit Testing Hadoop MapReduce Jobs With MRUnit, Mockito, & PowerMock

Posted by Michael Spicuzza on  Dec 03, 2012

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

Why Testing Matters in Agile Projects

Posted by Sharon Robson on  Oct 02, 2012

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

The Day the QA Department Died

Posted by Eli Lopian on  Sep 24, 2012

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

Tackling real-world unit testing problems

Posted by Gil Zilberfeld on  Jul 23, 2012

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

Testing SQL Server Code with TST

Posted by Roopesh Shenoy on  Jun 18, 2012

We explore the TST framework and a few ideas for writing and maintaining good tests for database code. 2

First Steps in Unit Testing

Posted by Gil Zilberfeld on  Jun 05, 2012

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

Writing a Comprehensive Unit Test

Posted by Jonathan Allen on  May 24, 2012

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

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2015 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT