Our clients have seen an ROI.

Applying automation using the DevTest Workstation for automation of middleware validation, has decreased manual effort by 40%.

It is hard to put a dollar figure on it. If you have multiple large development efforts and are sharing common test environments, CA Service Virtualization is a huge benefit because you don't have to schedule your testing based on when the test system is available. However, if you are a smaller shop with one development team who works serially, CA Service Virtualization is overkill.

We quantify what kind of benefits that we have against the cost that we have to pay on the solution. It turns out to be a really good exercise there. It forces us to do the ROI on the technology product that we buy against the benefits that we reap from the product there.

I would like to see some kind of dashboard that shows all of the dev test scripts that we have out there so that that we don’t have to rewrite the same ones across the enterprise. We can look to see what's there and reuse some of the ones that are there. Right now, it's hard to figure out what we have.

I would like to have some way to enable developers to use it more. They tend to like to go to JMeter before they do a dev test. The developers don’t need the UI and all the overhead that goes along with that. They already understand how to virtualize. I think it's a great tool, but it seems a little thick and heavy and it's very expensive. I think we are able to find open source solutions that do similar things. What I have found that I like is that I can use it to do my out-of-the-box things, like my batch testing and integrate some of my other tests and inflow that I don't get from other tools.

We didn’t calculate the ROI. We started this to save test environment costs, but we ended up with more testing and better quality.

ROI typically comes over a longer duration (both Service Virtualization and Release Automation), although its significant in terms of overall project cost when taking into account hardware, testing delays, and third-party dependencies.

Over about a year, we have saved over half a million for our customer.

We haven't yet measured ROI with the current implementation.

We have eliminated the complete dependency for all the backend systems for SVP (Stress,Volume and Performance). Testing using Service Virtualization saved huge amounts. Using service virtualization we have implemented a shift left concept to enable different teams to work in parallel instead of waiting for other teams to start the work, this also reduced the overall budget for the program.

ROI is NOT that great since the product license is expensive.

It really depends on various factors like the type of project and timeline of the project. Definitely ROI is a lot better then earlier projects when we didn't use virtual services.

Clients were able to save $700k and three million GBP in the first year of using the solution.