CA Service Virtualization Review

User-friendly, flexible, and saves us in development time


What is our primary use case?

  1. By virtualization, for all dependent services, we are able to create isolated test environments.
  2. We virtualize fragile services and deploy them with the 'Failover' mode so that we can fall back to the VS in case the real service returns an error.
  3. We virtualize third-party paid services, as well as in-development services, to minimize costs and delays.

How has it helped my organization?

In short, we are able to save a lot of valuable time. Testers and developers no longer complain about not having access to dependent services. We don't have to share/reserve resources or worry about our development being blocked by unavailable services.

What is most valuable?

The ability to create virtual services and deploy them as Docker containers, and include them in our Jenkins build pipelines, is a valuable feature.

It was critical for us to prevent possible elements from "unnecessarily" breaking the pipeline. If I'm pushing a particular web service through the pipeline and want that to be tested in isolation, it is a big problem if everything fails due to an irrelevant dependent service.

The use of containers provided a very flexible solution.

What needs improvement?

The workstation component has a very out-dated UI and is in dire need of a facelift.

There are too many fragmented web components that could easily and logically be merged. For example, Service Catalog, Enterprise Dashboard, Portal, and Identity and Access Manager are all separate web applications. Why not merge them in one web app?

For how long have I used the solution?

I have been using this solution for nearly two years.

What do I think about the stability of the solution?

This is a very mature and very stable product, although error prevention could be added into the product, for the sake of improving user-friendliness.

What do I think about the scalability of the solution?

The idea of Virtual Service Environments (VSE) makes the product extremely scalable. Especially with the use of containers, you won't have concerns about resource wastage.

How are customer service and technical support?

This solution has first-class support, and it couldn't be any better.

Which solution did I use previously and why did I switch?

I used HPE SV before. It was very user-friendly but cannot be compared with CA DevTest, as it lacks a lot of the important features.

How was the initial setup?

This initial setup of this solution is not straightforward at all. The installation is unnecessarily complex. Again, user-friendliness is not an area that CA DevTest can boast about.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest