Design for Testing Early

Understanding good software design is often about understanding issues of scale. Good code works efficiently and correctly when all of the inputs to the system increase exponentially. But issues of scale arise in more unexpected ways throughout an application's lifecycle. For example, a few lines in the requirements phase can translate to hundreds of lines in the design phase. This means that defects in requirements can generate far larger defects down the road. The bottom line? Testing has to be treated as a development effort of its own, with a lifecycle of its own, starting with a requirements phase. Gerold Rajesh of Virtusa elaborates in a podcast interview.

Posted by Kevin Carlson at 01:57 PM  Permalink