Parasoft Service Virtualization Bring-Your-Own-License
Parasoft | 2023.2.1Linux/Unix, Amazon Linux Linux 2 kernel 5.10 - 64-bit Amazon Machine Image (AMI)
Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Its an amazing software for virtualize your web components, 100% recommendable!
What do you like best about the product?
It helps to become the continuous testing a reality. Also is easy to use and intuitive!
What do you dislike about the product?
Sometimes it have bugs and it have a lot of diferents tools that become it some difficult to understand.
What problems is the product solving and how is that benefiting you?
It solve for example, if the web component of the ambient is down you can virtualize it and you wont have that problem again!
- Leave a Comment |
- Mark review as helpful
Parasoft Virtualize is a Masterpiece
What do you like best about the product?
Well, I have been using this tool for the last 2 years and this is helping us in all the critical scenarios we have. Not only that also it is helping us to do our customized scripting whenever required.
What do you dislike about the product?
Well, few features like Magic String capabilities are not available, I am surely looking for such soon which will increase our productivity.
What problems is the product solving and how is that benefiting you?
Firstly the components which are not ready along with Parameterized values, we can create such Services also putting Data, and it is just mimic of or real services which are helping testers along with the client for a positive approach.
Recommendations to others considering the product:
Great tool, just a few tweaking and helps to sort a lot of challenges.
Amazing product, create endpoints with ease
What do you like best about the product?
We have 2 environments with Virtualize:
1. Frontend HTML served by endpoints accessible by our 'acceptance' employees who will accept software companies. We build Virtualize endpoints with HTML pages, which from there we control Parasoft server as backend (like a website), so only administrators work at the tests in Virtualize and 'users' from the webpage.
The magical stuff happens in the backend, sending REST requests, handling responses and writing data to the repository, writing responses to the server hard drive as files, creating new variables like GUID and datetimes and 'tokens' and results are written to the repository and showed in the frontend!
2. Simulator of Healthcare data sources. Endpoints serving HL7 SOAP XML messages. Some incoming data we need to save in a Postgresql DB to serve later in outgoing messages. Some XML incoming messages we send to other servers to validate XML messages.
It's really easy to set up endpoints, create a response test, set up the body like whatever you want. With your mouse, you drag the project to the servers and the endpoint is already live!
1. Frontend HTML served by endpoints accessible by our 'acceptance' employees who will accept software companies. We build Virtualize endpoints with HTML pages, which from there we control Parasoft server as backend (like a website), so only administrators work at the tests in Virtualize and 'users' from the webpage.
The magical stuff happens in the backend, sending REST requests, handling responses and writing data to the repository, writing responses to the server hard drive as files, creating new variables like GUID and datetimes and 'tokens' and results are written to the repository and showed in the frontend!
2. Simulator of Healthcare data sources. Endpoints serving HL7 SOAP XML messages. Some incoming data we need to save in a Postgresql DB to serve later in outgoing messages. Some XML incoming messages we send to other servers to validate XML messages.
It's really easy to set up endpoints, create a response test, set up the body like whatever you want. With your mouse, you drag the project to the servers and the endpoint is already live!
What do you dislike about the product?
Something difficult to find a good solution, manuals are sometimes professionally written by experts.
What problems is the product solving and how is that benefiting you?
On the fly changes and customizable, flexible and almost everything is possible with custom tools, easy to copy projects, change and commit with SVN and to share with others users
Recommendations to others considering the product:
It's an amazing product, it needs some time to learn but you always get support
Does it all with ease!
What do you like best about the product?
My background is systems engineering, and network protocol analysis, so this tool sings to me, as I know when, where, and how to solve problems with this tool.
First off is protocol and data structure support. Most scenarios were drop in the driver jars and update the transport config in a UI tab.
We have done IBM MQ, Rabbit MQ, JMS, SOAP (XML), REST(JSON/XML). Synchronous, Asynchronous, time based, you name it.
Even complex MQ single request with multi-response. Blew away our app dev team how easy it was to simulate complex time-based systems. I was asked, why don't we use this tool in Production? Advice is though awesome, don't use it as a stop gap to build things in production.
Did I mention its easy? So many ways to solve problems, you can load a wsdl/swagger, etc. You can record traffic, or even build services out from ground up. It has built in and extensible data support, from an in-memory table, to csv, to NoSQL data repository.
Has even newer test data management capabilities which looked awesome, though we did not buy that add on.
Environment Manager is awesome ability to put the environment configuration control in front of the test team.
First off is protocol and data structure support. Most scenarios were drop in the driver jars and update the transport config in a UI tab.
We have done IBM MQ, Rabbit MQ, JMS, SOAP (XML), REST(JSON/XML). Synchronous, Asynchronous, time based, you name it.
Even complex MQ single request with multi-response. Blew away our app dev team how easy it was to simulate complex time-based systems. I was asked, why don't we use this tool in Production? Advice is though awesome, don't use it as a stop gap to build things in production.
Did I mention its easy? So many ways to solve problems, you can load a wsdl/swagger, etc. You can record traffic, or even build services out from ground up. It has built in and extensible data support, from an in-memory table, to csv, to NoSQL data repository.
Has even newer test data management capabilities which looked awesome, though we did not buy that add on.
Environment Manager is awesome ability to put the environment configuration control in front of the test team.
What do you dislike about the product?
Not really the tools fault, but there were a couple old technologies that were problematic 30-60yr old.
JDBC Virtualization works well against modern DB during POC and training, however, we had an older database protocol in our environment that was challenging to get to work.
We ended up using a tailored test data management tool from that same provider as the db.
We even experimented with reverse engineering a proprietary TN3270 protocol but did a cost benefit analysis and instead virtualized at another layer, which was way easier.
JDBC Virtualization works well against modern DB during POC and training, however, we had an older database protocol in our environment that was challenging to get to work.
We ended up using a tailored test data management tool from that same provider as the db.
We even experimented with reverse engineering a proprietary TN3270 protocol but did a cost benefit analysis and instead virtualized at another layer, which was way easier.
What problems is the product solving and how is that benefiting you?
Our initial problem was broad spectrum data alignment and time based eventing and response across 10-12 interfaces.
Previous approach of replicating non sensitive production data yielded inconsistent results. Prior to the tool the test strategy would be to poke around at data sets until found a scenario that worked. Which rarely worked, and if did, wouldn't work the next day.
By recording a day’s worth of data and customizing in desired scenarios and cloning in multiple highly desirable scenarios we could now test consistently and continually. Our internal reference was we now had a "Groundhogs Day" environment.
As a side note, early automation test efforts, it would take about 4 hours to completely fabricate a scenario by hand across all interfaces and events. Now with the tooling, it is just automatic.
Previous approach of replicating non sensitive production data yielded inconsistent results. Prior to the tool the test strategy would be to poke around at data sets until found a scenario that worked. Which rarely worked, and if did, wouldn't work the next day.
By recording a day’s worth of data and customizing in desired scenarios and cloning in multiple highly desirable scenarios we could now test consistently and continually. Our internal reference was we now had a "Groundhogs Day" environment.
As a side note, early automation test efforts, it would take about 4 hours to completely fabricate a scenario by hand across all interfaces and events. Now with the tooling, it is just automatic.
Recommendations to others considering the product:
Support is awesome. Could usually get to a live support person same day, or next day. Which is amazing. Their support knows the tool inside out and I was always able to show them my processes, and they would provide feedback immediately, or following day.
As bonus, during our POC, we had a special request for MQ configuration, and they were able to provide custom build next day. I mean who does that these days. Parasoft is truly master of their domain.
As bonus, during our POC, we had a special request for MQ configuration, and they were able to provide custom build next day. I mean who does that these days. Parasoft is truly master of their domain.
showing 11 - 14