There are several areas that are easily configurable. A person, without having a lot of development experience, should be able to perform most of the functions.

There are many different features available to build services with adequate response times, recording of visitors.

View full review »

A while ago, we were looking for a tool to do testing across the web services. During that time, we were doing some PoCs on SoapUI. We did a PoC with Lisa. The company name was ITKO. After going through several PoC sessions, we figured out that this would be beneficial because the functional testing, which we would be creating for those web services, could be leveraged for performance testing as well.

We have a conceptual testing document where we say, you run a single user-firing transaction against three simulators and you host your test there. Over a period of time, we matured from using web services to using all the web-based UI applications. The best part about it is that it goes one layer below the UI. It’s not dependent on the UI. It’s dependent on the transactions going back and forth between the application server and one layer below your browser.

Usually, with tools like Selenium, you just click. In this case, you post a transaction and test how far it goes.

View full review »

In the case of the virtualization of TCP/IP protocols for third-party terminal insurance, there was a device terminal, which was interacting with the application via the TCP/IP protocol. Most of the tools don't support that, but we were able to achieve it using Broadcom Service Virtualization.

View full review »

We have been using it extensively for the shift left process and testing. It helps us to accelerate and virtualize services and assets that we don't have. It enables to test faster.

View full review »

The most valuable feature of CA Service Virtualization is that overall, it is a system-based product for virtualizing the services. There are many tools that offer RESTful calls. However, with this product, we have many other options such as database service virtualization, mainframe virtualization and other wide range of virtualization options.

View full review »

It is introducing a lot more flexibility for us. It reduces time scales, getting time to market. It also helps us cross-skill some of the people, and start to really bring that DevOps mentality into the bank.

I suppose in our payments estate in the bank, it's key to us. Anything that we need to put through to payments, regulatory, industry-leading, that kind of thing, we need to get there quicker. It's expensive to maintain those complex systems. Virtualization gives you the opportunity to do that a lot cheaper. We can stand up those versions of it, rather than build the humongous end-to-end environments that they always require. It's helping drive that testing down to being a lot leaner.

View full review »

It's the ability to capture and replay traffic that's most valuable to us. We can monitor network traffic while getting data, and a virtual endpoint lets us see what the platform would respond with. We use it to isolate our app from unreliable pieces of the ecosystem, protecting our code from uncertainty.

View full review »

For CA Service Virtualization, it’s the ability to quickly prototype something. My guys really like the ability where they can do the recording session. It's a way for them to initialize for existing services where they need to get it up and running. The ability to have a listener and capture sample packets was a key thing that they really liked. It really helped us jump-start something. We could do something within an hour to have it up and initially runnin

Also, the ability to have the different back end connectivities, whether it's an Excel spreadsheet, or more complex things where we’re now linking the data sets and responses back together. Those have been a couple of the key areas for us and have been very beneficial. It’s also certainly a lot better than just doing stub code, because now I have templates that I can more readily reuse. That's better than just somebody who’s kind of building up the Java code to build stubs.

We keep running into situations where people will start building stubs and things like that, and we'll come back and show them the benefits of this solution. Once they start to see it in use, then they start to say “oh, okay, this is a lot better on that side.”

From a CA Release Automation perspective, it’s certainly the idea of being able to do the automated deployment. The challenges are that we started off down this path a few years ago, we purchases some licenses and have not taken full advantage of them to this point. We've had an ongoing challenge within our environment that stood up quickly.

Now we're getting a little bit more focused about this. I'm already doing some work on it and we’ll be doing more over the next few weeks. We’ll be looking at the Release Automation tools for coming up with the best processes for us to be able to have a repeatable process that quickly can deploy code without having to do a lot of manual steps. We want a good and clean workflow.

I think one of the things that we did appreciate was that changes were coming in to the product at a good cadence. We needed to support WebLogic, which was a big one for us at the time. Those things did come in, and we didn't have to wait a huge amount of time. I always felt like the product has been getting good updates to support us as we were doing some of those activities.

One of the things that we know and we're trying to work through is looking at when I go to set an environment up, maybe I don't quite have that new service yet, but I have other applications, my UI application, or whateveris ready to go, but I have this other middleware call that needs to be available. The idea that I can spin up or point myself to a virtualized service without one piece of it, but still use the rest of the end to end system, that's kind of one of those things that we would envision.

I'm doing a deployment of an environment / application, it's being configured, and then if I need to I'm going to use virtualized services for some or all. What we've been working on is how we can do a lot of that shift to the left by using service virtualization, so when we deploy we can at least get the development teams testers up and running on the application. Then we just have them virtualized on the back end. That might be how we would be setting up and configuring ourselves. It's definitely in that situation where you don't have a true end to end environment, but still need to be up and testing. That's where Service Virtualization would couple with the deployment in my book.

CA Test Data Manager is where there's one kind of end to end system and there has to be a system of data. A lot of times these call systems are hitting, and so having that model so that we can get it into the data, so when we deploy the software, you're going to bring this up. It may be our building data, which is an interesting challenge for us because it's a third party product, though they work very closely and have people on site with us.

Other systems that might need to have a configuration- there's all the types of users that are allowed into the system, or other types of price catalog information, whatever we want to model, that's where TDM is in your standing open environment, that's where you need to have something in place.

For some of our systems where we have to have data in it and available to product catalogs or something like that, then the TDM data can be very beneficial, and we can swap the data around, so we might be trying a new product catalog that's coming out, or new few features that are going to be offered, whereas we can also then go back to a production-like configuration as well.

View full review »

CA Service Virtualization has helped us advance the development cycle when third-party interfaces are not available to us. We're able to simulate that activity. Working with the developers, we're able to get our testing site done in advance, so that when the integration starts, we're able to get further down the testing path with our third-party vendors.

View full review »

To us, right now, it is going to be reducing the capacity limitation on mainframe, because we are highly dependent on mainframe capacity which is not easily available to us.

View full review »

The DevTest Workstation (JMS steps) and CA Service Virtualization are the most valuable features.

View full review »

Using the agile method, each iteration is scheduled to last 1-2 weeks and development would take up most of that. The testers didn't have enough time to properly test the application. With Service Virtualization, we virtualized the services and we brought quality into the agile iteration “extreme left”, and we started early testing.

That's how we got enough time to test the product. Service Virtualization helped us by using marks and stops. We are easily integrating with other applications and we are performing integration testing seamlessly. Before implementing Service Virtualization, services were not always available because of infrastructure issues or iteration time schedules. Service Virtualization removed all these problems that we were facing in the industry and allowed us to quickly do our job.

View full review »

The ability to virtualize test environments. This allows us to test on an environment without having to wait for time windows, thus eliminating a bottleneck in a traditional shared test system.

View full review »

Web service virtualization solution: It’s cost effective over a period of time and provides flexibility in product validation in the SOA space.

View full review »

The ability for us to be able to record the live transactions, and create a virtual services out of that, as well as be able to actually use the request and response to create new virtual services for the back-ends that we don't have access to. We have a bunch of use cases there from that perspective.

View full review »

• We mainly use it for performance testing.
• Being able to spin up virtual services without buying additional hardware and being able to test.
• Ability to shift left or simplify the SDLC process.

View full review »

Service virtualization is the most valuable feature because we can create end-to-end services without actual hardware, so that saves a lot of cost and money.

View full review »

The keys feature of this product are:

• Workstation, where we can perform web service virtualization. That is primarily our focus, to enable the development and testing team.
• We are creating mocking and stopping for service virtualization.
• We are moving shift-left, meaning to carry out testing on the back-end which is not available. That's the main feature for this product.

View full review »

It helps us to create service scripts for performing shift-left in our testing.

In the development environment during the early lifecycle, whenever there is a third-party interface that is not available, we use this product to create those steps that help us in getting responses, as and when needed.

View full review »

The features that I find most useful would be how easy it is to quickly get something up and running as a small test sample. The first test we had was simple transactions to it and emulating responses from there. We have Java and .NET APIs that we use to access the legacy system. Dev test works by hijacking the code and then you put an agent in it.

Also, it looks to see what classes you're calling. You can say, okay, if it hits this class, then I want to know. Then, the data that comes through there, you can analyze it and you can replay that data -- Java, .NET, or C#.

View full review »

The most valuable features are the recording and creating of virtual services. Especially in creating IBM MQ virtual services through recording.

View full review »

The ability to do parallel development and testing reduces our costs for duplicating environments, improving the productivity of our developers, and bringing products faster to market. 

View full review »

Service virtualization is the most valuable feature for us because there are fewer constraints through the SDLC cycle. It really helped us to remove bottlenecks and expedite the test time.

View full review »

• Codeless testing: There are no test scripts to write and maintain in DevTest. It helps to easily design test scripts without any programming knowledge.
• Complete test coverage for heterogeneous, distributed architectures: in a single test environment, DevTest invokes and verifies functionality at every layer of the application - from dynamic web UIs, to web services, ESB/JMS messaging layers, EJB servers, Java objects, databases, file systems, legacy objects and much more.
• Service Virtualization: Virtualization reduces the dependency of third-party services/system and allows us shift-left testing.

View full review »

It performs as advertised. We had a number of back-end services that were not available during testing times. What this had allowed us to do is get our early life testing done while those services are not available. 

View full review »

For service virtualization, you can have continuous testing and development without interruption to your test cycle. For dev test, I been able to customize to being able to test, automate batch testing, and integrate that with my API testing and UI testing. I have been able to use that as an integrator. I have had no issues with integration. We have been able to use custom code to integrate the pieces so we really haven't had too many problems with it.

View full review »

The virtualization options in the product: We can now virtualize entire backend systems or chains. That makes test and acceptance environments much more readily available, which offers more testing possibilities that results in better quality.

View full review »

Service Virtualization allows you to function in an isolated manner. It allows you to not be so dependent on systems that, in traditional testing, causes you delays, causes impacts to your overall time testing schedule, and just creates an efficiency in your overall process. It allows you to duplicate those systems or mimic them in a way that just creates greater efficiency and increases time to market overall.

View full review »

Virtualization.

View full review »

The most valuable features include the capability to use other program languages such as PLSQR, JAVA, .NET. This is important because whenever the tool is limited you can extend it by writing your own code. The code is not limited to a specific language, it can hold several types of coding language.

View full review »

It gives us the ability to simulate and virtualize components that we don’t currently have. This is invaluable.

View full review »

For us, the most valuable feature is that it gives us the ability to virtualize a lot of our integrated systems. That’s valuable because we have difficulty trying to coordinate all those different systems in terms of scheduling, timing, refreshing of data, and that type of things. It gives the developers freedom to develop without needing to wait for others; so it eliminates bottlenecks for us.

View full review »

I think the most valuable feature is the ability to quickly create simulations of APIs that you use to disconnect you from your dependencies as part of your testing process.

We've really done two different scenarios. One is the creation of a new API. We were able to create a simulation before we ever wrote a line of code, and so all of our customers who would use that gave us direct feedback very quickly. In a performance environment, we have lots of dependencies, lots of services that we talk to. Having the simulations gave us the ability to run test when we want rather than when they're available.

View full review »

The most valuable feature for us is that it provides configuration settings to make connections to the DB and web services. Because it has pre-written code exposed through an UI, it makes it much easier to configure tests.

View full review »

It's got a standardized format for endpoints as well as containerized, virtualized endpoints that are used by everyone on our team. We can spin up these endpoints if necessary.

View full review »

One of the key benefits is that it really reduces the need for an organization to have all these backend infrastructure systems which are very, very costly to actually procure and to maintain. Service Virtualization allows you to test without actually having physical backends there. It pretends that they're there.

By virtualizing application services, you can actually give them to whoever needs to use it. They make a request, get a response, and they use the application without even knowing that it's not connected to a real live system in the backend.

View full review »

The most valuable feature is definitely how quickly you can get up and mock something that’s not completely done. It’s very easy and it's extensible. You can add any custom logic that you need.

View full review »

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.

View full review »

You can create virtual services from a live recording or you can even take raw traffic and convert that into request/response pairs, and you can create an entire virtual service from just those simple little files, and that's super awesome when that all works out.

View full review »

The most valuable feature is the ability to virtualize almost any web service which allows us to perform testing and speed up our development.

View full review »

The biggest value for us was writing all the stories and figuring out what stories are going to get into which sprint. It also helps us with organizing the backlog and dependencies. We've found those features to be useful to us.

View full review »

The most valuable features are the web service harness and the service virtualization.

View full review »

• MQ virtualisation
• Web service virtualisation

View full review »

Quick setup of virtual services

Creation of virtual services by simply providing XML request/response pairs

View full review »

CA Service Virtualization (Virtualize) has been used to a greater degree, and Test has been used to a certain extent. The clients I have worked for purchased CA Service Virtualization with the primary goal of virtualizing web service calls to a specific back-end functions that faced constraints (performance, availability, and/or data constraints). By using CA Service Virtualization (Virtualize), they were able to overcome the stated limitations.

View full review »

We were using this product for service virtualization, and SoapUI/REST API testing for the US’s largest retail customer in the home improvement space.

View full review »

The ease with which we can create virtual services and view the flow in the model are valuable features of this product.

View full review »

• Web service virtualization
• MQ virtualization

These two features helped us to build a virtual development environment for continuous testing and continuous development of our product.

View full review »

The web services protocol for SOAP requests and responses is the most valuable feature. It is easy to set up the test for them without much coding, thus it is easy to train new testers to work on it in a graphical development environment where one can see the flow of information visually like the TIBCO product. It is easier than SoapUI to follow.

View full review »

The two most valuable features for us are:

• Service Virtualization – It provides us with the ability to replace real downstream systems with virtual systems.
• Test Automation – It enables us to trigger events and automate test cases.

View full review »

The most valuable feature is that it's available 24/7. If I'm not able to procure all the infrastructure and I have to share it, I'm not afraid to share it. It doesn't depend on who else is using it because I know it's available.

View full review »

The CAI aka Pathfinder is a great capability and will help the organization to achieve SV goals and expand the SV to different systems without many firewall changes or changes in the existing environment setup.

The financial industries have tight firewall security where introducing a new product among their existing infrastructure is not a hot cake or getting new MQs created for SV. At high-Level CAI looks like any agent-broker architecture but it does a lot in terms of Virtualization and Application Delivery Lifecycle where Dev or QA do not need to worry and do not need to depend on the environment teams to get the systems logs for triage or fix it.

Finally, last but not least CAI can also help the architects/designers to understand/generate the application flow diagram and analyse any abnormal behaviour.

View full review »

Pathfinder, VS Easy

View full review »

The most valuable feature is the ability to create systems. We use TIBCO for our integration; the ability to create those systems when they are not available to us is very effective.

View full review »

When we previously used CA SV we saw tremendous results, and went live with almost a 0% defect rate.

We use it for Service Visualization and to run tests to validate our services response with the database.

View full review »

Test - service layer component testing automation)

Virtualize - the best mocking/stubbing tool I've ever seen, allows for easier data management

View full review »

Very easy to create virtual services for test, Dev and training environments. Allows service creation by recording transactions or by loading WSDL. View full review »

The most valuable feature is that it supports so many protocols. We, being a large bank, have almost all the protocols, and it supports all of them, so that's one good thing.

View full review »

Virtualization is very important for me so as to mitigate my dependency on real back-end system and push the QA testing life cycle earlier.

View full review »

I like the fact that it allows us to focus on just the system under test. We can remove of all the dependent requirements from the system.

View full review »

It provides for automated testing of applications, including the following features:

• Wide technology support (SOAP/REST web services, message queues, web UI using Selenium, database queries);
• Support to build modular test cases using reusable blocks (called sub-processes in DevTest);
• Extensibility using Java;
• Integration with Jenkins continuous integration tool; and

• Detailed test execution reports.

View full review »

We do testing, so obviously the virtualized service is going to be our big use. A lot of the times, services and/or components are not available, whether it's because the equipment is not available or is being used for something else. With Service Virtualization, we can emulate services to test against them instead of waiting on infrastructure.

And it does it pretty well. We do the recordings and get the response-request pairs. We also have development groups that are probably going to be using these services because they won't let us test earlier in the life cycle.

We're actually ahead of the development groups on this, and they're looking into docking it, but they don't know how use it and they don't know how to create their own services. So we'll probably create the virtualized services for them and we'll support it, and then the development groups will test against our stuff.

View full review »

DevTest supports multiple testing environments so you can configure it to use one testing environment or 20, and you can change it for use in any other environments with the flick of a button.

View full review »

Record and learn response patterns: It helps us to record traffic and learn automatically response patterns. This feature helps us to virtualize quickly and build an exact copy of the web services.

View full review »

Service virtualization is the most valuable feature to me; it helped us to start the performance testing activities much earlier in the testing life cycle. It also reduces overall cost, as we can replace the expensive third-party services with virtual services.

View full review »

Virtualizing different protocols, data driving the request and response values, window to script if anything additional is needed from the virtual service.

View full review »

• Service Virtualization
• Web Service/MQ/Database Testing
• Selenium Integration
• Junit Integration
• ALM + Dev Test
• and a long list of other features.

View full review »

Its integration capabilities with other external tools and technologies - such as Selenium, JDBC, external JARs (which can be placed in /HotDeploy and used) - is quite impressive, as is its wide range of support for various protocols, such as FTP, FTPS, HTTP to TCP, etc.

Because I have been exploiting its features for web service virtualization, I like the way it provides a quick and easy solution in that area. The ease with which a virtual service can be generated with minimal inputs and quick time makes it favorable.

View full review »

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.

View full review »

We have a lot of different tasks to perform. We use and value all of the features CA Service Virtualization has to offer.

View full review »

Service visualization for almost all types of protocols. Version 7.5.1 has many improved features compared to version 6.5 which we were previously using.

View full review »

A couple of the most valuable features, to me, are the fact that you can have a lot of different people with different technologies use the tool, without any programming experience at all, all the way up to people who can program. And then, the more technical that you are, the more programming you have, the more you're able to customize the tool. Basically customize it to do what you want it to do. That's one thing. 

The other thing is, it's got probably the greatest amount of features, in terms of different technologies that you can automate and virtualize, out of any of the solutions out there. So, it really can accomplish any task that you want to do with it.

View full review »

• Flexibility
• Ease of use
• How much easier or faster we can actually make something happen.

View full review »

I use VSI, VSM, and SOA testing. I hardly use performance testing and automated GUI testing.

View full review »

It provides us a high level of integration with all of our solutions, to the extent that we can set up modules with Service Virtualization functionality at the same time. We will do more with it once we get more into it. So far, we have been using it mainly for services.

View full review »

The most valuable feature, and really SV's main feature, is the versatility of available protocols that cover a very large number of cases.

View full review »

This helps my team in virtualizing responses so we are not dependent on the systems when they are down. It also helps in mocking up a new functionality and virtualizing it which may not be yet dev-delivered. We also tried to automate services using LISA, but faced numerous challenges.

View full review »

We use it to have a highly-available development process because we develop our front end and middleware in tandem with our services teams. When their stuff goes down we don’t want them to cause us a delay on deliverables to the client.

Having a virtual service to rely on, we’re able to continue development even when one of their services fails. They provide built-in data handlers for a variety of different protocols. The REST data protocol auto-parses everything, so you can do analytics. It can flex and provide different responses depending on the request, and is easily measurable and repeatable.

View full review »

It's allowed us to be able to set up virtualization web services quickly and to test unhappy path scenarios. It’s easy to use in setting up virtualization and testing edge-case scenarios.

View full review »

LISA VSE and Test Cases.

View full review »

Supports lots of middleware technologies. Good virtualization tool.

View full review »

Virtualization and Functional testing.

View full review »

There are many valuable features!

• Recording to build models, even from non-trivial sources.
• Ability to vary the responses very easily (randomize, pick-lists, etc.)
• Useful for performance testing — highly scalable and can vary response times.
• 100% flexibility by being able to change models.

View full review »

Ability to virtualize webservices, MQ, JDBC

View full review »

Virtual services

View full review »

Service Virtualization

View full review »

Virtualization is useful for system testing where the test applications are not integrated.

Service virtualization is beneficial as it allows system and integration testing to be done, without depending on a fully available environment. This allows continuous integration and continuous testing

View full review »

The solution helps us develop applications faster.

View full review »

• Service virtualization (the virtual services created): Virtual service models are very well described and hence able to understand properly.
• Record and playback
• Creating VS from the DevTest console
• Magic string and data de-sensitization and model healing
• Reusing raw traffic files
• Wide range of protocol support, such as HL7 and many others

View full review »

It's simplified the automation process for SOA testing, where the tool provides most of the testing feature in-built, and the time spent on script development for automation is reduced.

We can now focus on the testing and providing customers with good coverage of requirements. The maintenance of automation suites is easier in Service Virtualization.

View full review »

• It supports virtualization for different combinations of transport and data protocols.

• It's easy to script for protocols that CA SV doesn't provide out of the box because it provides various ways to do so. Either by using scriptable data protocol, custom Javascript step or the CA SV SDK feature. CA provides a platform to use existing plus extended features all together.
• CA SV SDK, fllexibility to extend the tool.

View full review »

The new version of LISA (6 and higher) has an auto generator for stubs based on WSDL, WADL, messages request-response pairs etc. View full review »

• The description of the components that pop up when the mouse hovers over them

View full review »

Web service, MQ and IMS virtualization. The tool has many built in filters and assertions which helped us create better virtual services.

View full review »

Easy to understand ways of creating stubs.

View full review »