ValueOps ConnectALL Product Community

 View Only

The 12 days of 8.0 - Day 3

By Anon Anon posted Dec 03, 2014 06:01 AM


"On the 3rd day of 8.0 the CA Team gave to me,

THREE new execution modes

TWO RR pairs added

and a Server-Side Recorder in a DevTest tree!"


Welcome to our 3rd day of DevTest 8.0!  Today we're going to give you the gift of 3 new execution modes to help you efficiently keep your virtual service and live service in sync.  In case you need some background info on execution modes read: Harnessing the Power of Execution Modes


The 3 new execution modes add upon the 5 that are existing today to incorporate more ability for users to use both virtual services and live systems to respond match and respond to the requesting front-end application.

  1. Stand In mode first routes a request to the virtual service (same as Most Efficient mode). However, if the virtual service does not have a response, the request is then automatically routed to the live system.  Stand in mode doesn't do any special tracking.  It simply allows for a virtual service to fall forward onto the live service.
  2. Failover mode first routes a request to the live system (same as Live System mode).  However, if the live system does not have a response, the request is then automatically routed to the virtual service.  As you can see, this mode is the opposite of Stand in mode.  Failover mode can only be enabled when the virtual service is using the Live System/ Live Invocation mode - which means the virtual service is already looking for a response from the live system.
  3. Learning mode is like image validation mode but it automatically 'heals' or corrects the virtual service to have the new or updated response from the live system.  Now the very next request passed into the virtual service will automatically see the new response that was "learned".  The key here isn't that only one system is being checked to learn, but both are and the live system currently prevails.


So, how do you check out these new features?  First you have to record a new virtual service using the CA Service Virtualization 8.0 release (the virtual service model file has extra special routing that needs to be there for these new modes to work).  Next, deploy your virtual service, go into the Virtual Service Environment, right-click on the VS and select "Specify Model Behavior" to change the execution mode.  You'll then see the selection screen (depicted to the right) to select how you want that virtual service to route requests.


Learning mode has some additional functionality of taking 'check points' and saving the newly learned information back into your project area.  Our Senior Staff Software Engineer, Stephen Kress demonstrates this new functionality in this recorded demo:



As you can see, this new functionality is unmatched in the industry.  We're even more excited to hear how you plan to use it - let us know in the comments below.  And that's our 3rd gift to you on these 12 days of DevTest!



TThe 12 Days of DevTest Blog SeriesT

TWELVE Mobile Tests Generated

ELEVEN Selenium UI Test Scripts

TEN JSON assertions and filters

NINE API tests running

EIGHT Transactions Documented

SEVEN well calibrated agents

SIX Agents, protocols, categories intercepted

FIVE Generated assets

FOUR Opaque data types processed

THREE new execution modes

TWO RR pairs added

and A Server-Side Recorder in a DevTest tree!"