The one constant of software development is change. The rate of change has accelerated substantially in the last decade; the complexity of applications and environments has increased and schedules have been pinched. Under these conditions, software quality tends to suffer. If we are going to keep up with change and improve the software we are creating, we should find ways to optimize our QA processes. Improved testability is one way we can try to diminish the widening quality gap.

To understand the TAC architecture, it is necessary to understand the complexity of automation. The shortcomings of record / playback (R/P) methodology of automation are well documented. Many of the problems of R/P can be addressed by explicitly programming scripts. But programming is expensive and highly technical. Test groups often do not have the resources necessary to support such a programmatic automation solution.

One of the main reasons the Record / Playback (R/P) methodology of test automation usually fails to achieve set testing goals is that the paradigm does not sufficiently model real world testing. In order to understand this, we need to investigate several different but interrelated models. This document will discuss these models and then advance the Test & Automation Consulting LLC (TAC) Abstract Function model for test automation.
This document should be read in conjunction with the TAC Automation Architecture Document

High quality test automation does not happen by accident. It is the result of intense planning, concentrated design and solid software engineering. The automation architecture can be seen as the culmination of the planning and design phases.

Test & Automation Consulting LLC (TAC) custom crafts each automation project to ensure the highest return on investment (ROI) for each client. However, it is not cost effective for our clients to ?reinvent the wheel? each time around. Therefore, TAC brings certain automation testing artifacts to each non-trivial engagement.

Test & Automation Consulting LLC (TAC) understands that test automation is a software development process. Current automation tools do not supply all of the resources necessary to support a robust programming environment. Therefore, in order to best support our clients, we have created and maintain a number of code libraries and tools that add functionality to the commercially available automation tools.

The 12 Step Plan provides a guideline for how to gain control of the testing workflow process and how T-WorMS can help. This is an excellent place to start when thinking about implementing T-WorMS.