|
I agree with you David. I would only test the code that changed or was added. The requirement comes from our QA group or sometimes from my manager. I think some of it is paranoia resulting from a very serious bug that made it into production over a year ago. This exact situation hasn't happened yet so maybe I'm wrong but based on past experience it would not surprise me. If I was as organized as Rich and kept up with the programs I use to test new modules it might not be a big deal. To date these tend to be thrown together without thought to keeping them as formal testing procedures. As a result they tend to get discarded after a while. I think I see an opportunity for improvement here. Rick
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.