Friday, 2 May 2014

Do you have problems with your test environments?

Is one of the systems you depend on available only 2 days a week and you need it 5 days a week for testing?
Is setting up test data in external systems expensive or time consuming?
Are you paying unnecessary third party system transaction fees every time you run the same suite of tests?
Are you waiting for an external team to deliver an API you need for functional testing of your system?
You cannot performance test your application because a third party system can’t handle the load?

If you answered yes to any of the above questions you might find interest in learning about service virtualization.

For one of our recent clients, we increased the test infrastructure availability from 2 days a week to 7 days a week. A different client was able to test its software before an external team delivered an API she depended on. We have achieved that by replacing parts of the testing environment infrastructure with virtual services. We created them with the industry leading software for service virtualization.

For more details please visit

Traffic Parrot

1 comment:

  1. Great article! You might find it helpful to look at vendor neutral reviews of the Service Virtualization tools you mentioned on IT Central Station:

    CA, HP, IBM and Parasoft have all been rated and reviewed by real users, for example this QA Manager looked at a few different options before making his decision: "We considered HP SV, IBM GreenHat, Parasoft, and others. The benefits with CA SV are cost savings on hardware and earlier defect identification". To see the rest of his review click here:

    Hope this is helpful.