CA Service Virtualization Review

There is a range of different kinds of simulations that we can create, although integration of RAML files so that you can generate simulations directly from the specifications would be an improvement.


Valuable Features

The most important thing is that we can integrate it into our existing test automation and CI tool, which is Jenkins at the moment. Our plan is to elaborate the deployment process for continuous deployment – the integration of the testing tools is very important to us. We have real backends and there are already issues with availability and stability, so we use simulations to mock up the production environment.

Improvements to My Organization

There is a range of different kinds of simulations that we can create – capture/replay up to creation of real, elaborate simulations of the back end.

Room for Improvement

The UI is a pain point. If they had a better UI, it would have a much higher rating.

Integration of RAML files so that you can generate simulations directly from the specifications would be another improvement. For example, some guidance within the tool – if we could customize Service Virtualization, to disable functions we do not need. There are a bunch of functionalities which are part of the solution and we have to go through a number of cascading menus to find what we need. In other words, to simplify the front end.

We don’t, for example, use SAP or Oracle databases that we need to attach, and, therefore, it would be nice to disable these un-needed functions, to reduce the complexity of the GUI. Another point is that if something fails during the testing process, there is a lot of logged information that is useful because the error messages are Service Virtualization specific. It would be helpful to get more meaningful error messages. For example, a malformed JSON file, the error that is returned which is some internal error, but it’s not clear, for example, that it might be a syntax error.

Stability Issues

It’s great. The only problem we have is that the UI is not good. The tool is fully implemented in Java, and you can’t move readouts between screens. We can live with it, but we need a really huge screen. And we can’t work with a laptop.

This is one of the reasons we try to get rid of the UI and, instead, to generate templates by script so we don’t have to use the UI. We switched from using the UI to automatic template generation, which is a kind of model-driven testing.

Customer Service and Technical Support

It is very good. The response times are really short. We have a partner, IPT, a CA partner, whom we have engaged for support. So if we have some issues they call CA support, and the response times are really, really quick.

Initial Setup

It was already in production when I joined.

Other Advice

If you want to implement something at the enterprise level, then this is an appropriate tool, not something that is open-source or free. Think about how it integrates with other solutions and the product’s reliability. Also, you’ll need professional support for such a solution.


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