Testing-as-a-Service -Part 2

[geetika_shukla]

In the previous segment  Testing-as-a-Service -Part 1,I covered what is TaaS ,why is it required or how does it benefit Testing in an organisation. In this second Part ,I talk about Types of TaaS,when to go for it and in what cases is it not recommended.

Types of TaaS

We can have numerous types of TaaS based totally on the different categories of testing (They would overlap based on the broad criteria for classification e.g. Mobile /Game Testing can also be Functional testing and so on.)

Let us classify them briefly as:

1. Functional ->This includes unit and integration TaaS ,System and Regression TaaS,Acceptance TaaS which is mainly User Acceptance TaaS.
2. Non-Functional->The testing services here primarily are Security and Performance .

The Security testing service is formed mainly by 2 pillars :

a) expertise in risk based approach and mechanisms to detect various security vulnerabilities

b) adequate tools (Static and Dynamic)to conduct the relevant scans and tests

Performance testing service ,in the meantime,aims to check the load and stress levels of a product or application by simulating an environment of multiple users and other factors.One can also name singular and specifc TaaS types like the ones mentioned in the word grid above.

When to opt for Taas ?

When should an organisation specifically go for TaaS?

1. With the changing models to work and the move towards cloud ,the main trigger for TaaS is "On Demand" costing (instead of on-going)which is to say ,when there is a need ,you go for the service and pay accordingly.
2. When there is a need for the organisation to focus on the actual business rather than to build and set up an expert testing center.
3. When the key objective is result or outcome driven rather than the methods.This means that the organisation is interested to achieve the end results faster and pay accordingly instead of contributing to and paying based on the efforts involved in  the entire testing activity ,processes and cycles .
4. When there are clear-cut requirements and hence clear prospects of automation.
5. When the priority for the organisation is lesser investment (on testing tools ,environment,data ,licences ,resources ),more flexibility , scalability and lesser time to reach the market .

(Can you think of some more reasons ?)

When is it not recommended ?

A cautioned approach is advised before choosing TaaS in the following cases-

1. When the requirements for the organisation and need for automation is not clear .
2. When there is an in-house expert setting /sub-organisation to which all such testing activities can be outsourced.(In fact it is also an example of TaaS but within the org)
3. When confidentiality of artifacts ,project or any other involved element is of supreme importance.
4. When there could be an indication of conflict between the prospective TaaS provider and consumer in terms of legal agreements,intellectual property or discording nation laws.

(Can you suggest few other reasons for the same ?)

In the concluding blog ,Testing-as-a-Service -over the Cloud ,I will cover some aspects of Testing-as-a-Service over the cloud.