GeekArticles
Testing
Testing BasicsA Recipe for Change
Author: web.archive.org |
Published: 12th Aug 2005 |
Visited: 1263 times |
Add CommentFiled in: Testing BasicsIt needs to be remembered that the act of creating something new is inherently an act of destruction of some sort. Usually this is because you are asking people to give up something and remove it - even if that something was an anarchic process. It was still their anarchic process and something they were used to.
Read Article Sponsored Links
Related Articles
• Change Management for Changing Times Change is a constant of software development. Tracking defects, issues, and feature requests is a critical component of project success. When bugs are resolved early and quickly, lower development costs, higher quality products, and faster time to market are the likely outcome (along with the attend ...
• Auto-Reloading a unit after FileAttribute Change QC#: 58580 Version: 11.2 Status: Open defect, requires resolution Description: If you change a unit outside of the IDE, the IDE asks you if you want to reload it. However, if you only change the ReadOnly file attribute the IDE does not spot that. This ...