Most managers in small and medium size projects trust Developers for Testing. Please don't! I am stating this because, I am a Developer toO! Trust me nothing offensive here.
Naturally, at least as far as I experienced, developers are blind to some mistakes which are identifiable only by a non-technical Genius. Allow developers continue to innovate. Have a weekly review meeting with developers, testers and managers to discuss where things went wrong.
I am not totally against developers testing their module. Performing a unit test is an essential part of any developer's role. He could have understood the functional part but not as effectively as a functional expert do. Sometime, due to stress and late night builds, big mistakes on some usage scenarios goes unknown if not tested by testers other than the developer who developed it.
If your project budget don't allow you to add testers, try peer reviewing. However, you should try to accommodate at least one testing resource for functional black-box testing in every project irrespective of its size.
In my experience, I've realized many mistakes been unnoticed until a stage where it runs successfully for months or in some cases years. Yes, such missed mistakes are very rare to find and rarely affect the systems, otherwise could have been identified in the unit test or at least over a short term alpha or beta period.
But these rare mistakes could have taken away many orders in an e-commerce environment or missed many figures in a financial application or given a wrong guidance in statistical application. Trust me sometime spelling errors could take away the clients from you.
My sincere request to all managers: Despite the project size, please take testing as an serious part of SDLC. Don't wait till the last minute until the development is completed to test. Include testing as an integrated process and do frequent testing and implement an effective feedback system, where it could be efficient if the interaction happens directly with tester and developers on daily basis. Frequent mistakes could be bulleted for a weekly review with a power point.
Naturally, at least as far as I experienced, developers are blind to some mistakes which are identifiable only by a non-technical Genius. Allow developers continue to innovate. Have a weekly review meeting with developers, testers and managers to discuss where things went wrong.
I am not totally against developers testing their module. Performing a unit test is an essential part of any developer's role. He could have understood the functional part but not as effectively as a functional expert do. Sometime, due to stress and late night builds, big mistakes on some usage scenarios goes unknown if not tested by testers other than the developer who developed it.
If your project budget don't allow you to add testers, try peer reviewing. However, you should try to accommodate at least one testing resource for functional black-box testing in every project irrespective of its size.
In my experience, I've realized many mistakes been unnoticed until a stage where it runs successfully for months or in some cases years. Yes, such missed mistakes are very rare to find and rarely affect the systems, otherwise could have been identified in the unit test or at least over a short term alpha or beta period.
But these rare mistakes could have taken away many orders in an e-commerce environment or missed many figures in a financial application or given a wrong guidance in statistical application. Trust me sometime spelling errors could take away the clients from you.
My sincere request to all managers: Despite the project size, please take testing as an serious part of SDLC. Don't wait till the last minute until the development is completed to test. Include testing as an integrated process and do frequent testing and implement an effective feedback system, where it could be efficient if the interaction happens directly with tester and developers on daily basis. Frequent mistakes could be bulleted for a weekly review with a power point.
No comments:
Post a Comment
Share your comments