A development process that entails executing unit tests after the development of the corresponding units is finished. This ensures that the responsibilities of each software unit are well understood before the unit testing is done. Unlike test-first development, test-last development merely says that testing should be done before the code goes into production; it does not imply that the tests are automated. Traditional "QA" testing is inherently test-last development unless the tests are prepared as part of the requirements phase of the project and are shared with the development team.
Copyright © 2003-2008 Gerard Meszaros all rights reserved