CA Service Virtualization 8.0 has a new DevTest user interface to facilitate recording, editing and deploying virtual services among application development and test teams. This pre-conference session for CA World 2014 included this presentation to review each of the major features added to 8.0 along with an in depth demonstration.
Key Points:
Phoenix is a code name only. Will likely be launched as the “DevTest Dashboard” or “DevTest Portal” – a web based, non-thick client UI
We went through a methodical process to analyze functionality, workflows and most used features.
We next incorporated user feedback and a complete user experience design team (with constant review)
Last we built the designed elements and added functionality to those elements to help with “ease of use” and “user adoption”. We also were focused on delivering complete workflows in the new UI
Our goal is to continue to move workflows and functionality over from LISA Workstation to the DevTest Portalover the next few releases and eventually sunset the workstation in the next few years.
This is our first iteration of the new UI that will go into production. It is based on lots of customer feedback, interviews, design sessions and workflow analysis.
This UI also will help us architect our solution for more scalability in Cloud environments
Aquaria/8.0 will include both Workstation (thick client) and the DevTest Portal – you will be able to perform the same functions as you do today in the Workstation. The DevTest Portal includes both existing functionality, and some new tools. *EXCEPTION: PATHFINDER will only be in the new DevTest UI.
Only web, only HTTP recording
These are the benefits of using server side recording…
Only web, only HTTP recording
These are the benefits of using server side recording…
Only web, only HTTP recording
These are the benefits of using server side recording…
Only web, only HTTP recording
These are the benefits of using server side recording…
Only web, only HTTP recording
These are the benefits of using server side recording…
Learning Mode is automatic model healing execution mode
Only applies to newly recorded service images in 8.0.
Update to the model that includes new “Learning” assertions
- VS Image Response Selection step – includes “if learning” assertion
- Live Invocation step – includes ‘if learning” assertion
- Live System Failure – failover and standing in step
The available execution modes are:
(EFFICIENT) Most Efficient The fastest mode; it does not execute the routing or tracking steps. It also restricts generated event tracking.
(TRACK) Transaction Tracking This mode fires more events than Most Efficient and remembers transaction flow through sessions. This transactional information is used to help determine why a specific response was chosen for a specific request. This will not perform as well as Most Efficient. Transaction Tracking mode does not show live system responses; it only shows the response from the service image.
(LIVE) Live System This mode uses the Live Invocation step of the model to determine a response to the current request. Instead of using the response from the virtual service, it accesses the live service to get the response. The target system of the live invocation controls performance. This mode is also known as pass through, and is only available for web services.
(VALIDATION) Image Validation This mode uses both the VSE and the live system to derive a response to the current request. The responses are compared and appropriate history remembered. This mode allows a live comparison between the responses provided by VSE and a corresponding live system and, where differences exist, patches or heals the VSE service image to keep in sync with the live system. This mode is also known as "live healing mode." It is the least efficient of all the modes, and is only available for web services.
(DYNAMIC) Dynamic This mode enables the model to determine for each request which of the other modes to use. Performance is, therefore, unpredictable. This mode is only available for web services.
Mainframe Support
Support for CICS without needing copybooks
Immediately support all versions of CTG
SAP Support
No need to setup a gateway and re-register BAPIs
Better support for iDocs and RFC virtualization
Possibilities: Catch all
It probably can handle over 60% of data OOB
Handle any uncompressed data formats