This entry was posted
on Wednesday, February 21st, 2007 at 7:48 am and is filed under General.
You can follow any responses to this entry through the
RSS 2.0 feed.
Both comments and pings are currently closed.
As a long time project lead, I can attest to the fact that the success of any single development project weighs heavy across the entire breadth of any project team. As such, the development and continuous use of an automated test suite is one of those contributions to a software development effort that has a high multiplicative payback overtime, but is often undervalued in the present.
Once created and deployed, an automated test suite has the means to scale the efforts of a few, over the testing needs of many. Even after the QE team that developed the automated test suite [ ZatoIchi ] are no longer around, their efforts continue on, often out of sight, but never out of mind.
As a long time project lead, I can attest to the fact that the success of any single development project weighs heavy across the entire breadth of any project team. As such, the development and continuous use of an automated test suite is one of those contributions to a software development effort that has a high multiplicative payback overtime, but is often undervalued in the present.
Once created and deployed, an automated test suite has the means to scale the efforts of a few, over the testing needs of many. Even after the QE team that developed the automated test suite [ ZatoIchi ] are no longer around, their efforts continue on, often out of sight, but never out of mind.