Architectures for Good Software Testing – Introduction

Through out history architecture and engineering has created masterful physical assets such as bridges, houses and office complexes. Some constructions such as the Barnenez (France), Sechin Bajo (Peru), Mehrgarh (Pakistan) and Pyramid of Djoser



(Egypt) have lasted for thousands of years. Such amazing constructions require thought, planing and adherence to guidelines before, during and after execution. Although usually viewed as unassociated with architecture and engineering, software testing is the same.

Software testing is the last extensive effort before a solution is deployed. Due to tight timelines, budgets, issues during development and misguided business priorities testing is more often than not cut short with the view that endusers are the best testers. If Stonehenge were built according to this priority, our modern age would have been robbed of one of it’s greatest conspiracies (aliens yes or no: vote here).

These articles summarize what I believe to be the very basic architecture for testing software before it reaches the end user. Due to the complexity of developing software it is unrealistic to expect no application contains bugs, but reducing the issues to those which do not cause the enduser to lose faith in the solution must be the goal.

Finally keep in mind these requirements for solid infrastructure and quality assurance guidelines are written from a quality assurance manager’s perspective. I cannot stress clearly enough that the considerations included in these posts cannot be done without a strong collaborative approach. A strong group of stake holders must be included in this “architectural discussion”. I recommend drawing the stake holder group from the development, operations, customer support, sales and finance departments. If you develop broad consensus, enforcing the requirements of your quality assurance policies becomes much easier. It is entirely possible the ultimate outcome for your enterprise will look somewhat different as noted here. The quality assurance manager must know what is right for his or her company as decided in a collaborative and empathic environment.

Click here for part two – “Finding a Home“.

About Larry

Larry Lawhead is a passionate Agilest with a love for coaching, mentoring and organizational transformation. Huge fan of the Lean Enterprise, LeSS, Theory of Constraints, systems thinking and of course the Toyota Production System. Avid learner. Deeply influenced by the works of Jeff Sutherland, Eliyahu Goldratt, James Womack, Craig Larman, Faith Fuller, Marita Fridjhobn and countless others. He is likewise a member of the team that brings the Agile Open to the Southern California. Above all else, he loves coaching teams and individuals. He believes creating a safe and empowered place for individuals and self-organized teams to develop brilliant solutions, shared vision, demonstrate compassion and desire to continuously improve brings life’s greatest rewards. Watching clients unfold into a greater sense wholeness, purpose and direction is the miracle coaching enables. This satisfaction leads to continuous self-improvement, curiosity and personal growth that Larry passionately embraces.
This entry was posted in Architectures for Good Software Testing, Quality & Value and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.