Testing Strategies for Disfunctional Software Organisations - Conclusion

(Page 3 of 3 )

Find a Balance

Most organizations incorrectly attribute their testing woes to not being able to find the right testing personnel; but in reality, they fail at testing because of their approach. Good test practice involves planning early, striking a good balance between unit testing and system testing, making a strong, organization-wide commitment to quality, and establishing a framework that helps automate testing and provides greater visibility to senior management. Bringing in a QA architect early is probably the best investment a development team can make.

This approach to testing can greatly reduce testing costs and improve both developer/tester productivity as well as the overall application architecture. Indirectly, it improves the maintainability and reusability of the source code and helps you find defects early in the development cycle. It really helps every facet of your development process.

Note: If you have other successful test strategies that you'd like to share, I'd be interested in hearing about them. You can reach me at rajk@lycos.com.

---

Notes

Originally written by Raj Kesarapalli.
Copyright (c) 2000-2003 IBM Corporation. All rights reserved

DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

Comments On: Testing Strategies for Disfunctional Software Organisations

>>> Be the FIRST to comment on this article!