Skip navigation
All Places > DevTest Community > Blog
1 2 3 4 Previous Next

DevTest Community

227 posts

Today, we are excited to announce a new and lightweight way to define virtual services and achieve even faster time to value. We’re calling it CodeSV and it’s built to look just like a typical developer interface or IDE.  There is no need to learn a new tool because it works exactly as any software engineer would expect.


Here are some of the benefits for using CodeSV:


  • Simple - The simple, fluent, Java-based interface (API) lets developers virtualize HTTP traffic in just a few minutes. By using CodeSV, you or your team no longer need to spend unnecessary time configuring endpoints. Endpoints are auto-generated. “In-process virtualization” (IPV) artifacts are created on the fly, saving time and avoiding the annoyance of doing it manually.
  • Versatile - Request/Response (RR) pairs can be imported and exported so that virtual assets can be reused and even shared across teams. This eliminates the need to create new assets from scratch and, again, accelerating the time to test.
  • For Developers - CodeSV has been built by developers for developers. It supports virtualizing both REST and SOAP services. So, we’ve got your web service virtualization covered.


Built off the experience of a decade’s worth of virtualizations and testing, CA Service Virtualization is now optimized for your desktop. At its core, CodeSV is a lightweight yet powerful tool that brings real value through its simplicity, automation, and sharing features.


Best of all, CodeSV is a free tool you can download today from GitHub.


Support for SV as Code is provided as a Community effort and can be found under CodeSV Category on the DevTest CA Community. 


 If you ever need help with anything, here is the place for you. Here are simple steps to post questions to the community and stay informed:


  • Search Existing Content: Just type your question in the top box.



  • To start a new question, simply “Ask my Question. Enter the question, please feel free to attach documents if you think it’ll help.

  •  Before you finish posting, please make sure to tag (#CodeSV) your question. And most Important select CodeSV at the question’s category.


If you want to track all information tagged and categorized as CodeSV, you can simply select the Content Category File on the left panel. And if you want to stay constantly informed of the latest postings related to CodeSV, you can create a RSS Feed.


Enjoy CodeSV! And drop by our community to let us know what you think of the tool… 


Download today from page.


As you might already know (or not), End of Service for DevTest versions 8.1, 8.2, 8.3 and 8.4 are coming up soon on July 1, 2017. This means that the above mentioned versions will not be supported after July 1. If you are one of those that are still on those releases (or even prior ones), this would be a good time to start planning for the upgrade to the latest release of 10.1. 


I would be more than happy to discuss this with you. Please reach out to me at for any questions/concerns or to simply discuss the upgrades.



 - Koustubh

Now that DevTest 10.1 is GA, attached is an upgrade guide that will take you thru the steps and the important considerations for the upgrade to the latest and exciting release of DevTest.

Here is the location of the PDF - How To - Upgrade DevTest 8.x To DevTest 10.1 


Remember we now support in-place upgrade from 8.x to 10.1 which means you can install in the same location as your prior release and you can also use you existing database which will be upgraded automatically for the 10.1 release!!

Special thanks to mazda03 (Dan Mazzei) for updating the doc with the latest screenshots and new content.





- Koustubh

DevTest 10.1 - CA Service Virtualization /CA Application Test

We are pleased to announce that DevTest 10.1 including CA Service Virtualization and CA Application Test is generally available (GA) as of April 18, 2017.  We have several new and exciting features in 10.1.  Below are the highlights in our new release.  Keep an eye out for additional videos, how-to's and best practices as we head into the new year.


Key New Features in DevTest 10.1:


New – Create Virtual Services from Swagger 2.0 Specification using the DevTest Portal –  The DevTest Portal now supports the creation of virtual services described by Swagger 2.0 specifications (the de-facto standard for REST API definition)


New –  Implementation of Invoke 2.0 APIs in DevTest Portal – Creation of virtual services (via Recording, RR-Pairs or Specification) is now done using the new Invoke 2.0 APIs and provides an improved workflow experience


Key Enhancements in DevTest 10.1:


Enhanced - Support for Swagger 2.0 – Additional support for Swagger 2.0 when creating virtual services and test cases from Swagger 2.0 specifications in the DevTest Workstation:

  • Reference Object
  • Example Object
  • Form-Data Form type
  • Default parsing of optional parameters


Related Links


Download DevTest 10.1


Video - Create Virtual Services from Swagger 2.0 In DevTest10.1

What's New in DevTest 10.1

Release Notes - DevTest 10.1

User Docs - DevTest 10.1

Upgrade Center - DevTest 10.1


CA DevTest Team


Copyright © 2017 CA. All Rights Reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. This document does not contain any warranties and is provided for informational purposes only. Any functionality descriptions may be unique to the customers depicted herein and actual product performance may vary.

This How To blog is for those who signed up for the "Bring Your Own License" (BYOL) offering on either the AWS Marketplace or Microsoft Azure and need to insert their license and start the CA Service Virtualization tool. Here are the steps to follow to insert your license and start up the SV services on your new virtual machine.


1. Find your License Email. This is typically from a "" email address with the subject line including the words "License Activation". ATtached to the email will be a file called "devtestlic.xml". This is the file you need to add to your virtual machine.


2. Place the devtestlic.xml file in the install directory for CA Service Virtualization - C:\Program Files\CA\DevTest


3. Start the DevTest Services in the order listed below - Note all services are readily accessible on the bottom toolbar on your Desktop



  • 1. Start Enterprise Dashboard Server (wait until ready)
  • 2. Start Registry (wait until ready)
  • 3. Start Virtual Service Environment
  • 4. Start Portal
  • 5. Start Simulator
  • 6. Start Coordinator


4. Open the Portal UI and Get Started!

Double Click on the "DevTest Portal UI" and sign in with the default user name/password - admin/admin

Screen Shot 2016-04-12 at 2.57.53 PM.png


Here's a video on using the tool...

How to Get Started with CA Service Virtualization on Demand in Microsoft Azure - YouTube

When it comes to testing, core Java developers around the world tend to be a "do-it-yourself" bunch. And this is certainly true for testing components such as Java objects while they are under development. Testing Java classes and Java Remote Method Invocation (RMI) servers requires hours of tricky coding and test client development, so often developers will wait until much later in the development process to test, when the object is being rolled into a larger system.


Prior to the introduction of tools like CA’s DevTest Framework for Java & RMI, Java class or framework testing was only possible with a programmer's IDE in Java or JavaScript. Since this code-based approach can only be used by the developer, often when they are in the middle of coding the app, the tests that emerge often take the "happy path" of testing only for the conditions the developer expects.


Better unit and regression testing practices (with JUnit/Ant and other tools) have become par for the course in enterprise Java development. This offers a starting point for quality, but unit testing alone is simply too manual to properly exercise your components early in development, when problems are much easier to fix.


To really exercise these complex components early, we need to stop writing code to test code. We need to test the functionality and performance of the component - not create new volume of scripts to test. We need to help the QA and business requirements owners test to functionally validate our components, earlier in the project. CA’s DevTest was built from the ground up for this purpose. The DevTest framework includes CA Application Test and CA Service Virtualization.


Features Include

  • Inline testing.Break the code-compile-run-curse cycle, and never write a test client again. Execute test while you're authoring and adjusting them. You will have to see to believe the level of continual feedback you get while you are developing with DevTest.
  • Built on and for Java. DevTest is pure Java, and is innately aware of Java objects and RMI at a granular level, whether they are under development or "legacy" components you need to leverage. As you should expect, DevTest runs on any Java-ready client (Unix/Linux, Win, OSX) and can easily test objects on any Java-compliant server.
  • Easy enough for non-developers. DevTest is no-code automated testing, meaning developers save time by no longer having to script tests. Non-programming QA and business requirements team members can also get involved in testing the functional logic of these components.
  • Multiple systems. One DevTest test case can follow a complex workflow and validate multiple web sites, web services, Java objects and application servers. DevTest supports active sessions, SSL, authentication and magic strings, so it lets you test systems just as your end users will. On the back end, DevTest provides live interaction and deep testing of any component or service you can access over the Internet.
  • Across the full development lifecycle. Test components iteratively during development with immediate point-and-click responses. Then roll those same unit and functional tests into regression tests included in your Ant/Make builds. Then take those same test cases and turn them into load and stress tests that can run continuously



  • DevTest for Java/RMI provides an ideal automated testing environment for Java objects and components, offering a new level of breadth and depth that allows the entire team to own quality.
  • True no-code automated testing with compelling features for both developers and QA professionals.
  • Eliminates the need to program test clients and maintain fragile test scripts.
  • Provides an immediate way to accelerate "test first," XP development practices.
  • Brings QA into the iterative development cycle for early and continuous testing.
  • Works with any J2EE application server (Java App Server, WebLogic, WebSphere, JBoss, more).
  • Leverages and runs with your existing build and deploy environment of JUnit/Ant scripts.
  • Point-and-click testing of Java classes, RMI, and other objects (CORBA, etc.) in a way no other product can.
  • Browse, analyze and make live assertions against any available logic or controls in the application.
  • Manage properties and test assertions.
  • Turn your Java/RMI test runs into load tests, and scheduled regression and performance tests over time.
  • Great for analyzing and testing legacy code and objects that you may need to integrate.
  • Test instrument your custom application code with the powerful Extension SDK.
  • Built for the future keep your test cases and extend them to web interfaces, EJBs, JMS queues, JDBC databases, web services and JMX metrics.
  • Share test cases and test runs as simple XML files and incorporate them into your existing groupware, issue tracking and requirements management processes.

CA’s Application Test - The Test Harness for Custom Java Applications

Are you running proprietary or custom software? Where most testing solutions would give up, DevTest’s integration abilities let developers "test enable" software. With minimal incremental effort, developers can make their code testable with our simple API. The whole team can get rich metrics and debugging information on applications behind the scenes.

The more complex your enterprise applications are, the more compelling testing with DevTest becomes. Quality is not just a tool you can buy, it is an experience your whole team needs to own.


Take a closer look at DevTest today – check out our latest intro product tours:



CA Application Test provides a single platform to execute the automated tests across systems, APIs and services. Test execution can be performed cross-browser and on mobile, and can use real devices, simulators, labs or cloud platforms. CA Application Test builds portable, executable test suites that are easy to extend, easy to chain into workflows with other tests, and simple to integrate with existing test repositories. With workflows the results from one test can be used to feed and kick off the next test saving hours of time and enabling continuous testing.

Multiple verification steps can be chained together. A test step is a workflow test case element that performs a basic action to validate a business function in the system under test. Steps can be used to invoke portions of the system under test. These steps are typically chained together to build workflows as test cases in the model editor. From each step, you can create filters to extract data or create assertions to validate response data.

The tool can include any type of different component verification steps. Below is an example of a multi-step test that crosses various layers of a financial application.


Multi-step test cases can be then staged together into test suites and then executed in a single command. A test suite can be combination of different tests, so if user wants to setup sequentially test one channel e.g. Web and then Test Mobile they could accomplish that as well.


You can test the interface. You can test your source code. But how do you know the "loosely coupled" components of your application are talking to each other? Messaging is the core connection point for any distributed application. Until now, your options for testing the integration that connects the dots on your infrastructure were largely manual endeavors.

The automated testing tool that speaks the language of your systems

CA Application Test, part of CA’s DevTest Framework, for JMS provides teams with a no-code way to discretely and deeply test messaging queues of almost any known flavor. Rather than forcing you to custom code or adapt a test client, CA Application Test can become a test harness that publishes and subscribes to JMS frameworks. Finally, without a massive implementation effort, you can decouple your systems for flexibility, and test for reliability at the same time.


CA Application Test was built from the ground up for distributed architectures. If your strategy relies on JMS messaging to enable cross-component and cross-application integration, you should take a closer look at CA Application Test for JMS.

  • Inline testing. You'll never write a test client again. And you will execute while you're testing. You would have to see it to believe the level of information you can get while you are designing and maintaining JMS frameworks with CA Application Test. Break the code-compile-run-curse cycle.
  • Built on and for JMS standards. CA Application Test can talk and listen to most known JMS frameworks. As you migrate systems, you can get a wealth of reusable test cases and accompanying validation of your asynchronous messaging environment over time.
  • Multiple roles. CA Application Test is no-code automated testing, meaning developers can invoke JMS calls without having to script tests, and non-programming team members in QA and business requirements teams can also get involved in testing on their own terms.
  • Multiple systems. CA Application Test is pure Java, and is innately aware of Java objects, EJBs, RMI, JMS queues, JDBC databases, web services and JMX metrics. As you should expect, CA Application Test runs on any Java-ready client (Unix/Linux/Solaris, Win, OSX) and can easily test any server that routes JMS. CA APPLICATION TEST provides live interaction and deep testing of any JMS messaging you can access locally or over the Internet.
  • Across the full development lifecycle. Roll the same unit and functional tests you design into regression tests included in your Ant/Make builds. Then take those same test cases and turn them into load and stress tests that can run continuously from CA Application Test Server.



  • Advanced publish and subscribe abstraction layer to test and load JMS frameworks for any message queue protocol (TIBCO, IBM MQseries, more).
  • Allows you to rapidly and deeply exercise JMS messaging queues across disparate systems, including guaranteed delivery settings and JNDI.
  • Create and/or assume temporary JMS Queues and Topics to snoop through the entire life cycle of a message as it move from message handler to message handler.
  • Validate that web services, EJBs and Message Driven Beans (MDB) are receiving/sending the appropriate message payloads.
  • True no-code automated testing with compelling features for both developers and QA professionals
  • Eliminates the need to program test clients and maintain fragile test scripts.
  • Provides an immediate way to enable "test first," XP development practices.
  • Brings QA into the iterative development cycle by including JMS calls within their test cases.
  • Works with any J2EE application server (Java App Server, WebLogic, WebSphere, JBoss, more).
  • Leverages your existing build and deploy environment of JUnit/Ant.
  • Browse, analyze and make live assertions against any available logic or controls in the application.
  • Manage properties and test assertions.
  • Instantly turn all unit/functional/regression test runs into load tests and scheduled performance tests.
  • Set alerts for boundary or failure conditions within any test run.
  • Test instrument your custom application code with the powerful CA Application Test Extension SDK.
  • Share test cases created in CA Application Test and test runs as simple XML files and incorporate them into your groupware, issue tracking and requirements management processes.


The Test Harness for Custom Applications

Are you running proprietary or custom software? Where most testing solutions would give up, CA Application Test's integration abilities let developers "test enable" software. With minimal incremental effort, developers can make their code testable with our simple API. The whole team can get rich metrics and debugging information on applications behind the scenes.

Testing Software AG/WebMethods-powered Integration, Business Process and SOA applications Enterprises adopt the Software AG suite to accelerate the development and alignment of IT around the core processes of the business. But whether you are approaching Software AG (webMethods) solutions as an enterprise integration challenge, or using the company's IT governance platform, CentraSite, as a way to embark on an SOA strategy, quality is essential from the start. CA's DevTest Framework includes CA Service Virtualization and CA Application Test and offers Software AG (webMethods) customers a no-code way to test, validate and virtualize every layer and every phase of Software AG implementations - at design time, run time and change time - ensuring trust in your critical business applications.


Ensuring Quality and Agility for webMethods Customers

The possibilities for deploying Software AG (webMethods) solutions for enterprise application integration (EAI), or as an enabler for SOA (Service-Oriented Architecture) initiatives, are as limitless as the ways a company can configure its business processes. But one aspect that all Software AG (webMethods) customers share is a need to integrate heterogeneous technology assets - from legacy apps to newer technologies - to build a larger business context. Conventional testing methodologies can be both costly, and ineffective in these environments.

Why is achieving test automation so critical in Software AG (webMethods) integrations?


  • High cost and effort of test creation and maintenance. Conventional UI-oriented and unit test coding approaches take a procedural approach that results in brittle tests that are invalidated by dynamic change in the system.
  • Lack of complete validation of the business workflow. Many testing tools oversimplify the approach for messaging and BPM workflow testing to only component testing at a single endpoint or messaging technology type.
  • Quality must maintain a business context across multiple layers of the application. In order to validate that a business requirement is met, integration testing must not skip verification of any of the layers in the architecture, whether these layers are newly integrated, or under the authority of a third party.
  • Inability to test at every stage of the application lifecycle. Testing as an "acceptance" phase or event prior to deployment can no longer provide sufficient coverage for a constantly changing, heterogeneous application structure. Quality must be a continuous part of design, development, build and deployment in order to ensure trust in the application.
  • Constraints due to unavailable or "not yet ready" services and components limits agility and lengthens delivery times for needed functionality. Virtualization of these components is needed to enable distributed teams to design and deliver functionality in parallel.



  • CA’s DevTest framework is a comprehensive automated testing, validation and virtualization tool built from the ground up for SOA and composite application integration. If your integration strategy relies on SAG solutions, CA Application Test's declarative, no-code testing approach offers a compelling solution for maximizing delivered quality and minimizing business risk.
  • Native integration with CentraSite Active SOA. Out of the box, DevTest directly interacts with SoftwareAG's CentraSite platform, providing an immediate reference point for adding Quality to your overall Service Management and SOA Governance efforts. The ability to validate Policies - and SOA endpoints - both at a management and an implementation level with CA Application Test, ensures reliability and Trust that the system will work as defined.
  • Built for messaging standards. CA Application Test can talk and listen to webMethods Broker messaging layers, as well as most known JMS/MQ frameworks. As many implementations must integrate with - or migrate functionality from - other systems, teams using CA Application Test can get a wealth of reusable test cases and accompanying validation of the asynchronous messaging environment over time.
  • BPM Process-aware functional and load testing and verification. Break the code-compile-run-curse cycle. CA Application Test is no-code automated testing that normalizes your integration layers into a common, point-and-click test interface, allowing developers and business stakeholders to validate software in business process terms. Tests are highly reusable as orchestrated validation suites. CA Application Test extends the value of these efforts to performance testing activities, to verify that scalability or latency issues do not appear in production.
  • Multiple integrated systems. CA Application Test is pure Java, and natively tests Java objects, EJBs, RMI, JMS queues, JDBC databases, as well as web services (WSDL/SOAP) and file systems. As you should expect, CA Application Test runs on any Java-ready client (Unix/Linux/Solaris, Win, OSX) and can easily test any server that routes JMS. CA Application Test provides live interaction and deep testing of any applications assembled using SoftwareAG integration platforms.


 Features of CA Application Test for Software AG

  • Make live assertions against available services and implementation layers in SAG and webMethods-based integrations, both for business functionality, SLA validation, and as load and performance testing for IT Operations activities.
  • Create and/or assume temporary Broker JMS Queues and Topics to snoop through the entire life cycle of a message as it moves from message handler to message handler. Validate every layer of SOA or composite apps, ensuring web services, HTTP, Broker, and JMS endpoints are receiving/sending the appropriate message payloads at a unit level, or as part of the same test workflow.
  • Ensure integrity of migrations by validating file systems and transferred data within any JDBC data source. No need to program test clients and maintain fragile test scripts. Developers and QA teams stay engaged in testing throughout the application lifecycle with a high level of test automation and reuse. Business process owners can utilize CA Application Test's subprocesses to understand the validity of a process - even if they do not know exactly what components are tested.
  • Rich test metrics and feedback (SNMP and others) from webMethods Optimize, with monitoring and alerting to report boundary or failure conditions within Integration Server or Broker.
  • Virtualize dependent components with CA Service Virtualization across all technology layers within the SoftwareAG implementation, including Web Services, messaging services, data sources and underlying systems, allowing 24/7 availability of a valid environment for testing and validation for parallel development and integration.
  • Create a baseline test from a set of transactions in the using the Application Insight functionality.


DevTest for Software AG/webMethods - Testing, Validation and Virtualization Across the Platform



CA Application Test coverage for Software AG integration efforts.

CA Application Test provides teams with a 360-degree view of the quality and reliability of the application, and its underlying implementation layers, throughout its lifecycle at design time, run time, and change time.

Extending quality within your implementation process

The partnership of CA’s DevTest and Software AG extends beyond software, because an SOA strategy isn't something you buy, it is something you do. Best practices for Lifecycle Quality using CA Application Test fits within Software AG's best practice methodologies, and the end result is increased reliability and reduced cost and implementation risk.

In addition, enterprise applications will always contain some legacy or custom functionality that needs to be tested in order to fully validate a business process. CA Application Test Trace Kit's integration abilities let developers "test enable" software. Test Runner lets you incorporate tests into a continuous build workflow. Or, use Test Runner with JUnit to run standard JUnit tests in Ant or some other build tool. The whole team can get rich metrics and debugging information on applications behind the scenes.

The Continuous Validation Service in CA Application Test orchestrates the testing and validation aspects of IT, Integration workflows, and SOA Governance, to ensure reliability and instill trust throughout the lifecycle of the application. CA Application Test is part of CA’s DevTest Framework and conducts live regression, functional and performance monitoring of critical business workflows on a continuous basis, providing an actionable way to enforce that expected business policies are being met.

The Challenge: Solving the Unintended Consequences of Change in Enterprise Apps

Distributed enterprise applications will naturally evolve over time, as they leverage highly interdependent and changing services and technologies, which are assembled to build the finished application at runtime. Continuous integration is moving from a best practice to a do-or-die IT tactic. With so many heterogeneous components working together as an application, there is no specified "release date" for a new BPM process flow, or a new build of the components underlying your enterprise applications. When a service is added or changed, it has the potential to cause a "ripple effect" on other dependent upstream and downstream workflows.


In order to manage the business risk of this change, companies seek to employ IT Governance practices, to ensure that Management, Policy and Testing are all incorporated into the application development and deployment strategy. CA Application’s Test "Always On" testing provides a key enabler for quality, ensuring that expected Policies and business requirements are reliably met.

How the Continuous Validation Service Works

The Continuous Validation Service in CA Application Test can be used as a shared provider of both scheduled and event-based regression and performance test suites. When a change to an underlying application is made, when a new service is promoted for use, or if an unexpected error or performance expectation is not met, CA Application Test can communicate with the enterprise's stakeholders, or report this activity to an SOA governance, ALM collaboration tool, or IT monitoring platform.



With Continuous Validation in your environment, you gain a strategy for mitigating risk in your enterprise applications at build time, run time and change time, bridging the trust gap between Governance initiatives, and the actual software development and deployment lifecycle.


Thorough, repeatable validation and testing that runs according to your process, and takes your entire extended application into account, pays measurable dividends: avoided failures, reduced testing and release costs, alignment of IT with business goals and policies, and best of all a good night's sleep.


  • For integration activities, instead of having to figure out if a given build succeeded or failed by poring through unit tests that might provide little result data, the CA Application Test can report detailed conditions directly to the tester or governance platform as a gateway for the release. This protects the integrity of the existing workflows already in play, and drastically accelerates the process of build/adjust during release thanks to Application Test’s deep contextual feedback to the developer.
  •  For live deployed applications, CA Application Test provides extreme visibility into the entire SOA architecture, both at a component and system-wide level, as it continually evolves. The ability to manage such extensive and detailed test suites, with a project hierarchy for flexibly building and scheduling test processes, with automated dashboards for stakeholders to use, creates an easy to use collaborative system for enterprise quality teams. 
  • For governance practices, deeply enhanced dynamic test registry and test suite management tools give your team an actionable set of verification assets, thereby ensuring that SOA Policies for the compliance and behavioral needs of the business are actually being met by the combined services

What is the cost of application failure in your mission-critical applications? Mandating a Policy or a Service Level Agreement is a great way to start, but real functional and performance verification with CA Application Test is where the rubber meets the road. CA Application Test can provide you with a picture of the health of your Critical Software on a continuous basis, which is what you need if you are relying on mission-critical enterprise applications.

To learn how to use the Continuous Validation Service go to:


Invoke and verify is a term unique to CA Application Test and refers to the products ability to test and validate response across all layers of an applications with a single test. This unique ability makes CA Application Test a great fit for organizations that need to test applications that must work with legacy systems, custom applications, ESBs and back-end databases. For example, if we want to check that an order was placed from a Mobile device under test, we may look within an enterprise service or Order Management System to validate the proper order entry - only when these two/three validations are complete can we state that we have validated the functionality.


In CA Application Test, API and non-API tests are created in the same way, using a code-less visual designer, one test can include API and non-API tests. SOAP, REST, general HTTP based APIs, JMS Messaging, Java, and more are supported. Users can model a single test case with steps that invoke and verify an API’s behavior and performance, as well as validate database calls, SOAP messages and many more types of transaction Test can contain a mix of any type of underlying technology step types, across any number of APIs.


  1. First, Application Test Connects to an object on the application server, or over the Internet.
  2. Next, Application Test Gathers information about the component, showing you available methods for interacting with it.
  3. Then, you can Invoke, or the target system with a method, to create a result.
  4. CA Application Test then gets the Response from that object as a behavior - so you can make a test assertion against that behavior as part of your testing process.
  5. CA Application Test can then React to that response and invokes the next step in the testing workflow.


Since CA Application Test is an integrated testing suite, the value of Functional Tests continues, and tests are Reused in other processes. For instance, you can save the response data within a database, use that data to validate the behavior of another component or sequence of steps, save that functional test sequence as part of a business workflow, check the workflow in deployment at load, and then monitor its performance within a set of workflows... the list goes on.


To learn how to use the invoke ability in CA Application Test 10.0 visit:


To see a quick tour of CA Application Test visit:

Test Data represents a significant challenge for many QA and development teams resulting in time-consuming manual testing efforts, excessive costs and slipped delivery dates.  CA Service Virtualization can automate the creation and management of test data by capturing and manipulating virtualized datasets from messaging streams and data sources. These unique capabilities help eliminate test data conflicts between teams and drives lower costs and manual effort.

Common Test Data Management Challenges Include


  • Manual Test Data Management. Modern, distributed applications require test data to be created and synchronized across multiple systems, consuming significant time and manual effort. Accessibility constraints can make test data synchronization an almost impossible task, prompting testers to skip or reduce test scenarios.
  • Data Volatility. Systems under test often run against systems that are in production or shared by other teams. This causes the data to be volatile (changing randomly and often), making validation of results against these volatile systems difficult or impossible.
  • Data Sensitivity. Use of production data is limited by the need to obscure sensitive information such as account and social security numbers, and can present a significant compliance challenge, particularly when offshore or outsourcing service providers are used.
  • Impact on Production Systems. Some test scenarios create transactions that impact data in production systems. For instance, if a test places an order, the order then needs to be traced and deleted. This incurs time and costs on both testing and operational staff and can disrupt business operations if not carefully manage


Virtual Test Data as a Solution


CA Service Virtualization provides an automated approach to capturing, modeling, desensitizing and maintaining virtual test data across multiple services, integration layers and systems of record.


  • Virtual Dataset Creation: CA Service Virtualization listens and captures data as it flows across all application tiers and technologies to generate a robust virtual data set with a high level of functional accuracy. Test data can also be imported from databases (JDBC, SQL), Excel spreadsheets, flat files, log files, or XML sources.
  • Test Data Manipulation: CA Application Test makes it easy for testers to modify datasets and chain them together into scenarios. Data models can be created and edited within CA Application Test in a point-and-click environment with rules applied for randomization, sequencing or appending of additional data sources. Or, manipulate data in familiar tools of choice such as spreadsheets.
  • Test Data Masking: Sensitive live data can be obfuscated and automatically processed by CA Service Virtualization into "safe test data" that is valid for testing activities without violating regulatory or security policies.
  • Dynamic Data Stabilization: CA Service Virtualization can stabilize test data so that test scenarios are validated according to expected business rules. This includes maintaining the relevance of variables including changing dates, currency conversions, customer session information and sequential data entry steps.
  • Data Model Self-Healing: CA Service Virtualization can "self-heal" virtual test data sets by validating and recapturing relevant data from live sources or transaction streams on a scheduled or exception basis, increasing the long-term viability of virtual test data and minimizing the need to correct or update data manually.


CA Service Virtualization Benefits for Managing Test Data across Modern Applications


  • Reduced time and cost. Synchronization of test data across multiple dependent systems can be automated with LISA. Testers can now capture and build robust virtual data sets that automatically self-update for longer term use.
  • Eliminates constraints from the software lifecycle. Robust virtual datasets can be leveraged by multiple teams, enabling parallel development and testing activities without dependencies on live systems or conflicts over the use of shared test data.
  • Security and compliance. Automated masking of sensitive data allows testing to proceed without exposing data to unauthorized users or processes.
  • Reduced impact on live systems. Virtual datasets allow you to avoid accessing production systems to insert, update or delete test data.  Test data requests can be routed to virtual data sets or live systems in conjunction with exiting Application Lifecycle Management (ALM), Test Management (TM), and SOA Registry/Repositories as appropriate.



CA also offers a comprehensive Test Data Management solution – CA Test Data Manager. To understand when to use CA Service Virtualization vs. CA Test Data Manager read the blog: “CA Service Virtualization meets Grid-Tools – CA Data Finder how will they get along”.

CA Service Virtualization /CA Application Test

We are pleased to announce that DevTest 10.0 including CA Service Virtualization and CA Application Test is generally available (GA) as of December 21, 2016.  We have a lot of new and exciting features in 10.0.  Below are the highlights in our new release.  Keep an eye out for additional videos, how-to's and best practices as we head into the new year.


CA Service Virtualization 10.0 Highlights:

  • New workflows for creating tests
    • From an existing Virtual Service 
    • SWAGGER 2.0
    • WSDL 
    • RR Pairs
  • Updated support for Virtual Services created from SWAGGER 2.0
  • VS Config to change HTTP configuration of existing VS’s in the DevTest Portal
  • Integration API for automating VS creation in SWAGGER 2.0
  • New Integration with CA API Management- Capture the request and response data for APIs that are managed by CA API Gateway. Then create baselines and virtual services for the APIs. (CAI)
  • Mainframe Enhancements
    • Mainframe Transaction Virtualization with full agent configuration, transaction creation and virtual service creation right in the DevTest Portal. 
    • CICS Virtual Service Recording and Copybook Bundles in the DevTest Portal
    • Added support for CICS transactions that contain fragmented comm areas and CICS LINK Temporary Storage Queues (TSQ)
    • Support for CTG 9.2 and below
    • Mainframe Support for CICS in Portal from Capture
    • Added transaction lists to Copybook Mapping Tab

CA Application Test 10.0 Highlights:

  • Import and Create tests in Swagger 2.0
  • New Integration with Agile Central (Rally) automatically sync test run results from the DevTest Portal to the CA Agile Central tool.
  • New HP ALM Plugin for DevTest 64-Bit so that you can load and run a CA Application Test test case as a Quality Center test from the HP Quality Center suite.
  • New Coordinator and Simulator views in the DevTest Portal


Related Links (Be sure to check back after the new year for additional links, instructions and videos)


CA DevTest 10.0 Release Notes

CA DevTest 10.0 Product Documentation

Top Ten Reasons to use DevTest 10.0 from CA World


AusNet Services is Victoria’s largest energy business, delivering electricity and gas to homes and businesses across the state.



For energy companies such as AusNet Services, business outages are not an option. To keep its operations running, the company must ensure its complex IT systems are available 24x7.



AusNet Services uses CA Service Virtualization to virtualize its heavily integrated systems, enabling comprehensive testing before any upgrade goes live.



CA Service Virtualization has enabled AusNet Services to take a test-driven approach to development, with developers responsible for creating their own test cases. This means testing starts much earlier in the development cycle, reducing the volume and impact of defects.


Read the full story here: AusNet Services Minimizes Disruption from System Upgrades with CA Service Virtualization - CA Technologies 

During the month of July 2016, here are the updates to ideas. The goal of these monthly updates is to give you one place each month to see which ideas statuses have changed so that you can focus your attention to the updates that may be important to you and your team.


The list below is sorted by the status and then the category or product. For details on why the status was changed, just click on the link to the idea and check out our comments and notes.


Delivered: These features are GA! Comment on them to tell us what you think of them.

Currently Planned - We have these in our backlog as a high priority and our team is working to get them into the next major or minor release. Your comments are valuable here as we're in the process of building.

Wish Listed - We agree these are important ideas but either need more information or don't have it planned yet for a release. We've placed it in our agile backlog for prioritization. Vote for these ideas to move them up the priority list!


Not Planned - We don't feel these ideas are aligned to our product strategy. They are not planned for now or future.