DPTASM 04: No Test Automation Factory. No Scripting Office. No External Cloud.

What is it not about?

1. No Test Automation Factory: We simply do not want to set a Test Automation Factory up to produce Test Automation mechanism or infrastructure and ship individual instances of that to various Project or Product teams in an organization. If we do that, we will just lose most of the prominent benefits that "DPM’s Productized Test Automation Service Model" has potential to deliver.

2. No Scripting Office: And, we are definitely not talking about establishing a Scripting Office that is going to create custom Test Automation scripts and pass those on to various Project or Product Teams. We just want to create only once instance of Test Automation Common Infrastructure (TACI) and use that to provide Test Automation Service to Product or Project Teams across the organization.

3. No External Cloud: We are neither talking about an instance of Test Automation Infrastructure that resides in cloud (external to the scope of the organization). At this point in time, there is a greater possibility that your organization has already invested money and time in tools, infrastructure and people in the context of Test Automation. And, you are probably in a position to create your own private cloud hosting those tools and infrastructure.

We are talking about an instance of Test Automation Common Infrastructure (TACI) that you own at an enterprise or organization level. And, your organization is in complete control of the Test Automation Common Infrastructure (TACI) in question. In that sense, we are talking, rather, about an instance of a Test Automation Common Infrastructure (TACI) that resides in a cloud internal to the organization. Let's take a look at the description of this model in terms of its attributes, next.   Next Page >>

Comments

Popular Posts