Skip navigation
All Places > DevTest Community > Blog > 2014 > December
2014
Arif_Muhammad

DevTest 8.0 & Licensing

Posted by Arif_Muhammad Employee Dec 19, 2014

To provide maximum flexibility as well as control to our customers, in 8.0 we made following main changes from licensing perspective

 

  • Removed all license enforcements: In previous releases, our DevTest solution components e.g. Workstations, Registries etc. were individually licensed and needed to talk to licensing server for license enforcement. We felt that this restriction was hindering product adoption and utilization, so we removed all those license enforcements. Starting 8.0 none of our components need to talk to the licensing server or need a license file except Enterprise Dashboard which is further discussed below.
  • Enforced license audit data collection: As we transition from license enforcement model to honor based compliance model, we wanted to give the administrators the ability to have insight into the usage of the tools and components so that it help monitor compliance. So we made Enterprise Dashboard a mandatory component along with the need for Enterprise Dashboard to be activated via a license key file. The idea here is that only authorized administrators (having the key file) should be able to install Enterprise Dashboard so they have the full knowledge and control of Enterprise Dashboard instances within the organization and run audit reports off of. When Enterprise Dashboard is in place any number of registries could be installed just by pointing to an active Enterprise Dashboard, by anyone within the organization without the need of license file. Since all DevTest 8.0 components will be connected to the Enterprise Dashboard directly or indirectly, they will be sending usage metrics over to the Enterprise Dashboard. Those usage metrics are used by the administrators to help stay compliant and catch any unintended out of compliance situations. Here is diagram that shows how DevTest Components interact to push usage data to Enterprise Dashboard

Screen Shot 2014-12-18 at 1.28.41 PM.png

  • Report on New licensing metrics along with metrics used in old licensing model via Enterprise Dashboard: We understand that it will take time for customer contracts to move to newer licensing metrics. So we have both old licensing metrics as well as newer one being collected and reported via the Enterprise dashboard. What that means is that you can upgrade to DevTest 8.0 while you are still on old licensing contract and use the same tools to stay compliant. This will also give you a good understanding of utilization by newer metrics while you are on old contract, so that when contract renewal or change time comes you can make your choices based on the real data.

 

  • Giving control to Administrators to stay in compliance:  Next question is how can administrators be in control to keep organization going out of compliance. This is the only area where we are helping only from newer licensing metrics perspective. Since newer licensing is all user based (instead of component or transaction count based) we tied the control via ACL. The Access Control List gives the administrators to allow/restrict users to access different DevTest capabilities. Within our DevTest Server Console, we added information to allow administrators easily translate user roles into effective license. Please see below screenshot of DevTest Server console where effective license user type is shown based on selected permission list for each role.

Screen Shot 2014-12-18 at 2.32.59 PM.png

When a user with that particular role, logs in using any of the DevTets interfaces including DevTest portal, Workstation, command line utilities e.g. TestRunner etc. based on the role s/he is assigned, the effective license type is used and marked as an active user of that type for the time period s/he was active. This information about user being active is sent over to Enterprise Dashboard which collects information about all the active users and generate data on overlapping user sessions across different license types. This data is used to report maximum number of concurrent users for each user type in a given period which can be compared against the contract to asses compliance. Administrator also can see more detailed report of user sessions that can help them optimize the license usage.

 

Note: Indirect Run-time users of DevTest Services are not currently included in audit reporting. These are the users who are mainly manual testers not directly logging into DevTest portal or Registries. Those indirect users are testing user interfaces going against the Virtualized services or back-end servers monitored by CA Application Insight Agents.  

 

Please feel free to provide your feedback on these changes and anything else we can do to make your life easier in terms of managing and administrating the solution licensing.

Yes we hit 1,000 - four significant digits today!it_photo_94156.jpg


Thank you members of the DevTest Community for reading, commenting, answering each others questions, and adding ideas. 


Today our little community started just over a year ago hit it's first milestone, 1,000 YES, One Thousand members strong!


I know the DevTest PM team, (Stefana, Ian, Arpi, Arif, Bharath and myself) are impressed with all the Idea's posted in our weekly reviews.  I say this with mixed emotions as we look at the new ideas and review the ideas with the highest votes realizing you guys out number us 166.66 to 1 but we are up for the challenge.  Invite your friends and co-workers to the Community and customers take the next step and join the DevTest Customer Validation community so we can move it into the 4 digits also.


How Can Service Virtualization Transform Your Software Delivery Lifecycle?

 

By now you’ve heard the claim ...  every business is in the software business.

But what does it really mean?

 

It means apps, digital services, and APIs are becoming the primary customer interface for your company, and a key channel for driving revenue and brand engagement.

 

And it means, to put it bluntly, you have to innovate to survive… delivering new, high-quality applications FAST!  As more businesses transform to interact with their customers through digital channels, you have to make sure you aren’t left behind.  That means your software delivery lifecycle better become an accelerator, not a hurdle, of bringing digital innovations to market.  This is why DevOps is becoming such a hot topic, hoping the methodology will put organizations in a place to succeed.

 

Agile Parallel Development is the new DevOps capability that unleashes development velocity.  Service Virtualization is the technology that makes it real.  CA Service Virtualization accelerates the time-to-market of higher-quality, more resilient applications that are easier to deploy and manage.  It simulates the behavior, performance, and data of dependent systems, allowing teams to develop in parallel.  By automatically creating virtual systems (NOT just virtualizing your server or network), you can mimic the nuances of production environments without waiting on others, 3rd party APIs, or trying to free up constrained resources at midnight to test for quality.

 

And more and more enterprises are seeing the amazing ROI of using CA Service Virtualization.  MFUG Union Bank has reduced the costs for testing cycles by 65-85 percent!  While Tech Mahindra cut bugs in production by over 1/3!

 

The Next Generation of Service Virtualization is Here!

At CA World 2014, we announced Service Virtualization 8.0.  Simply put, this the biggest, baddest Service Virtualization release ever!  DevTest 8.0 (the new UI and full integration of CA Service Virtualization 8.0 , CA Application Test 8.0, and CA Continuous Application Insight 8.0) has the largest number of new features in any one release, largest number of new Patents, brand new web-based UI, and the largest number of customers and partners who participated in the Beta program. Each are fully available as of December 12, 2014!  And all are designed to help your organizations develop and test in parallel. Highlights include:

 

  • DevOps Analytics:  CA Continuous Application Insight (previousl CA Path Finder) automates the process of creating and maintaining virtual services and simplifies the production and management of automated test suites through the use of live application traffic captured in pre-production and production. This allows business workflows to be quickly discovered and mapped to help expose complex application architectures and potential performance bottlenecks.  8.0 introduces advances mapping paths and overlays, agent calibration to see the right transactions, and Splunk Integration.
  • Easy to Use: Our new DevTest Portal/ Web UI makes virtualized service creation easy. More than just a slick, completely redesigned user interface, our team focused on optimizing the most used processes to make them faster and easier to use.
  • Automated Learning Mode: Keeping virtual services sync to real ones is very challenging. Learning Mode compares responses between the virtual service and live system to automate the creation and updating of virtual services.  Just set it to watch the live system and apply any differences to the virtual service automatically OR save the changes for later application.  That easy!
  • Artificial Intelligence:  A new feature called Opaque Data Processing adds true artificial intelligence to the creation of virtual services without requiring any knowledge or decoding of a service protocol.  It applies a genome sequence alignment algorithm and discovers byte-level patterns in message protocols.  You can now virtualize a much wider range of protocols than ever before. No other vendor offers this advanced technique for virtual service creation.
  • Mobile App Testing: Mobile apps now account for over 80% of all new software development, and 50% of all e-commerce.  It’s up to you to make sure these new apps work!  Now you can automate your functional testing and application flow to create tests and find defects of your mobile applications.  Learn more in this mobile testing demo series and mobile test explanation video
  • Virtual API Cloud:  A free, SaaS offering giving customers the ability to create virtualized RESTful APIs via an intuitive website.  In just minutes developers can create, provision, and share the tools they need to deliver solutions faster.  Check it out today at vapi.ca.com.

 

These new capabilities are all capture in an amazing 12-blog/demo summary on our DevTest Communities page. Trust me, it won’t disappoint!

12daysofdevtest.jpeg

If you music is your thing, see how we put all of the newness in a music video to the tune of 12 Days of Christmas

 


Leading the Market with Innovation

 

Here is something important to understand.  CA (via ITKO acquisition) invented Service Virtualization.  We created Service Virtualization market, even coining the term. We are the leaders, and know this space better than anyone else!

 

And with the DevTest 8.0 release, we are extending our leadership and innovation. We now have been awarded 22 total patents (with a total of 28 filed) in the Service Virtualization market!  These include patents around Opaque Data Processing (artificial intelligence), Swift for bank transaction processing, Mainframe & SAP virtualization, a virtual systems learning mode, and around composite, database, batch, and run-time performance virtualization.

 

Another great example of our continued innovation is our partnership with ATOS.  We recently announced our joint CA Service Virtualization and Agile Testing Centers of Excellence (COE) for an end-to-end “Agile Testing” approach that allows developers, testers and performance engineering teams to work in parallel for faster delivery, higher application quality and reliability.

 

Try for free with Virtual API Cloud (VAPI)

And finally, we have brought the first wave of SaaS-based API Virtualization to the web fully available right in your browser with our CA Virtual API Cloud (VAPI) product.  Now, you can easily create and manage "virtual APIs" to simulate the behavior of the components required to test your applications under test.

 

We have been working hard to make building virtual APIs as simple as possible, and making it available in the GitHub developer community.  This community is intended to provide a place to learn, engage, and teach others about APIs, Your Virtual APIs and ways to improve VAPI to help meet your needs.

 

Sign up with your GitHub account and start today!

 

The Momentum is Just Beginning

This is just the beginning of great innovation to come around Service Virtualization.  It’s whole purpose is to ignite innovation around DevOps, and to help organizations thrive in the App Economy.

 

Make sure you register for the “What’s New in 8.0” Community webcast on December 16 where can see and hear all this new functionality in one place!

 

Merry Christmas and Happy Holidays everyone!

kelia01

The 12 days of 8.0 - Day 12

Posted by kelia01 Employee Dec 12, 2014

"On the 12th day of DevTest the CA team brought to me 12 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 processes,

THREE new execution modes,

TWO RR pairs added,

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

 

On the 12th day we received twelve gifts; 12 tests automatically generated from your Mobile Application - almost too many for Santa to hold in his sack.

santa-sack.jpg

Way back before CA World '18 we discussed Voyager Mobile Testing Monday #5 and we showed a Demonstration of Voyager at CA World too.

Watch Voyager Construct Tests and Run them:

 

We also have a  wonderful Dev Test Christmas Story told through your favorite Christmas Movies (Voyager is in there somewhere too!)

 

So now for your Christmas Story...

Everyone is making their way to Mobile for Christmas...

giphy (2).gif

They knew they could not make it in time unless they let their delivery really fly by leveraging Service Virtualization, just like Rudolph...

giphy (3).gif

Like Cousin Eddie Says: You want your Mobile App to be "Something Really Nice", so they knew they needed to test the app at every build...

giphy (4).gif

But the code changes every time its released and this breaks your tests... And that can really rob some of your Christmas Spirit...

giphy (5).gif

Add in fast delivery cycles from Development and the chore of updating and modifying your tests starts to feel like something that only Buddy could find fun in...

giphy (6).gif

Some may wonder if there is simply nothing that can be done to deal with faster delivery, and some run away in fear...

giphy (13).gif

Well the Grinch might find it satisfying, to see so many fear...

giphy (7).gif

But we have an answer in Voyager you'll see, the Dev Test team is like George Bailey - "Offering you the Moon"...

giphy (8).gif

Well almost,  we won't get you the moon... but Voyager can help you create tests for your Mobile App; and those may be created every time there is an application change, it can rebuild your testing catalog all by exploring your application - Its smarter than Buddy but just as excited to help...

giphy (11).gif

So this Holiday Don't Feel like your "Home Alone" when it comes to building Mobile tests, Voyager will help show you the way!

giphy (12).gif

Like a comet across the sky!

giphy (15).gif

Merry Christmas to all and may your Mobile app dreams come true!

giphy (14).gif

The End.

 

 

Wishing you and yours the Happiest Time of the year, a wonderful Christmas and Holiday Season!

 

--------------------------------------------------------------------------------------

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!"

--------------------------------------------------------------------------------------

 

"On the 11th day of DevTest the CA team brought to me 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 processes,

THREE new execution modes,

TWO RR pairs added,

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


Welcome to our 11th day of DevTest 8.0!  Today we are looking at the new CA Application Test capability around Selenium  powered UI test case maintenance and management


In 8.0 we enhanced Selenium based Web UI test case creation and management by 3 aspects.

Making target URL and Form Data variable: During selenium script import process we now automatically generate variable for target URL to make it easier to run the same test against different targets. We also added the capability to define properties for the form data so that you can use the script against different input data. Here is a quick video to demonstrate this new capability.

 

 

Bring it back to Se Builder for editing: We added a Selenium plugin that will allow you to import the Selenium based CA Application Test cases back into Selenium Builder so that you can use the recorder capabilities of Se Builder to add/modify UI steps. Here is a quick video to demonstrate that capability.

 

 

 


Configure Selenium WebDriver using DesiredCapabilities: We also added the ability to configure the WebDriver based on the desired capability configuration you can provide. You can place Desired Capability conf file anywhere in your project and point to it using "selenium.WebDriver.DesiredCapabilities.filePath" property. Here is an example of the configuration

          Screen Shot 2014-12-10 at 3.26.46 PM.png

      Here is an example of the Desired Capability configuration file. We do provide a copy in our samples. This allows you to configure behavior of the WebDriver including

      setting timeout values etc.

       Screen Shot 2014-12-10 at 3.27.24 PM.png

 

--------------------------------------------------------------------------------------

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!"

--------------------------------------------------------------------------------------


"On the 10th day of DevTest the CA team brought to me 10 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 processes,

THREE new execution modes,

TWO RR pairs added,

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


Welcome to our 10th day of DevTest 8.0!  Today we are looking at the new CA Application Test capability around JSON based REST API Testing


Prior to 8.0 if you need to parse JSON formatted response from REST APIs you have very limited choices. Either you will have to convert the JSON into XML and use XPath (does not always work) or you will have to parse the response yourself. In both cases some form of coding was necessary. In 8.0 we are making JSON formatted data first class citizen. Using new set of Assertions and Filters you will be able to directly work on JSON data using JSON Path.

 

Quick look at JSONPath:

 

Like XPath JSON Path allows expression based query and filtration of JSON data. In the expression top level or root of JSON structured data is referred by $ sign while nodes are separated by dot (.) notation. For illustration purpose I will use following modified form of data from tutorial.

{      "id": 2,

        "name": "An ice sculpture",

        "price": 12.50,

        "tags": ["cold", "ice"],

        "dimensions": {

            "length": 7.0,

            "width": 12.0 },

        "warehouseLocation": {

            "latitude": -78.75

        }

}

Using the dot-notation and $ as the root you could refer to length as $.dimensions.length. This expression will return 7.0. Array notation can be used to retrieve specific element of an array. In above example tags is an array and if I want to get 1st tag, I could use the expression $.tags[0] which will return "cold".  You can get more info on creating JSONPath expressions from http://goessner.net/articles/JsonPath/.

 

Using JSON Path based filters to query data:

 

    New JSON Path filter will allow you to add a filter as shown below.

Screen Shot 2014-10-07 at 6.12.55 PM.png

The JSON Path Filter needs 4 attributes to be filled out. Basically input data in the form of CA Application Test property, JSON Path expression and two output property names to hold the result and result count. Following is an example of getting the names of all the objects with length less than 7.

Screen Shot 2014-10-07 at 6.11.49 PM.png

After the filter execution is done the name(s) will be saved in property called allObj1 while count can be found in property totalObj1. Please note that the return value might be an array or a single value depending upon the query result.

 

JSON Path based Assertions:

    We added 3 main assertions to make it easier to validate the JSON based responses, as shown below.

Screen Shot 2014-10-07 at 6.12.13 PM.png

  1st thing you would want to validate is the structure if the response conforms to the expectation. For which we added JSON Schema based validation assertion. The assertion takes Schema and the payload as input and validate if the payload is conforming the schema. Here is an example.

Screen Shot 2014-10-07 at 6.10.39 PM.png

For design time assistance we are also proving additional details in case the data is not conforming to the schema. Here is an example of the design time assistance where schema requires property name2 be there but payload is sending name instead.

Screen Shot 2014-10-09 at 10.26.50 AM.png

For data value validation we allow both equal and contain assertions. Equal assertion matches the result of JSON Path for exact value, as shown below we want to make sure that object with id=3 has length 3.1.

 

Screen Shot 2014-10-07 at 6.10.59 PM.png

 

 

Contain assertion gives bit more flexibility for array based data. Following we are validating that an object with id=3 exists in the payload we are validating.

Screen Shot 2014-10-07 at 6.10.28 PM.png

 

We believe these filters and assertions should help tremendously in testing REST based APIs. Do you have JSON based APIs? Looking forward to getting your feedback.

 

--------------------------------------------------------------------------------------

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!"

--------------------------------------------------------------------------------------


"On the 9th day of DevTest the CA team brought to me 9 API Tests Running,


EIGHT transactions documented

SEVEN well calibrated agents,

SIX agents, protocols, categories intercepted,

FIVE generated assets,

FOUR opaque data types processes,

THREE new execution modes,

TWO RR pairs added,

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



Welcome to our 9th day of DevTest 8.0!  Today we are looking at the new CA Application Test collaboration capabilities that allows team members to execute, monitor and analyze test results.

 

One of the new and shiny toy you are going to see in 8.0 is our  DevTest Portal. The goal of the portal is to makes it easier for your team members to collaborate. Many of you asked ways to share standard automated tests that can be initiated with click of a button without the need of running workstation. Further the team members should have an easy to analyze view of the test results so they can see what exactly was exercised by the test and if it failed what was the reason of the failure. I believe we have made a good progress on this front. In this blog I will walk you through some of the capabilities.

 

For illustration I will be using following test case "Validate Car Inventory Look up" which uses combination of REST and Selenium steps to validate inventory API (using new cool json based filter) as well as verify that the CARS Web application, presents right data to the user as a result of VIN Look up.  Please note the naming of the steps, assertions etc.

Screen Shot 2014-10-10 at 5.09.39 PM.pngAfter creating the test I published it into repository called "ResHub" (Short of resource hub). This is basically a file system based repository of standard DevTest content you would want to share among the team members.  After logging into the new portal the user is taken to a dashboard as shown below.

 

Screen Shot 2014-10-10 at 4.53.11 PM.png

        Screen Shot 2014-10-10 at 4.54.38 PM.png

 

 

 

From left hand panel user can navigate into different DevTest portal capabilities, he has access to. To explore what tests are available the user will click on Manage menu item where he is presented with available projects in the ResHub as shown above. As you see Demo80 has 2 automated tests and one test suite which can be executed using the right click "Run" context menu. Once the test is initiated user is taken into monitor page where the status of all the tests in different state is shown.

 

Screen Shot 2014-10-10 at 4.55.22 PM.png

 

As you see the summary section shows the count of tests in particular state and the list provides the high level detail of those tests. You can drill into a particular test and see what exactly the test did. By clicking CarsInventoy test I started before, I see following test execution detail page.

 

Screen Shot 2014-10-10 at 5.58.36 PM.png

 

Most exciting thing about this view is that, you not only see the steps executed but also see filters, assertions, data-sets and companion in their execution sequence. Which makes it very easy for even someone who is new to the Application Test see what the test did. For advanced user who wants to analyze further expanding the activity will provide lot more detail. For example below you can see not only the request and response of the REST call but events and properties for further analysis of the test result.

 

Screen Shot 2014-10-10 at 5.59.03 PM.png

 

Following is one of the selenium step which verifies the VIN number in VIN lookup response page.

 

Screen Shot 2014-10-10 at 6.00.10 PM.png

 

The goal here was to make it easier to execute and review functional test results. Do you think this will help your teams to be more effective in achieving better collaboration?

 

--------------------------------------------------------------------------------------

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!"

--------------------------------------------------------------------------------------


"On the 8th day of DevTest the CA team brought to me 8 Transactions Documented


SEVEN well calibrated agents,

SIX agents, protocols, categories intercepted,

FIVE generated assets,

FOUR opaque data types processes,

THREE new execution modes,

TWO RR pairs added,

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

 

Screen Shot 2014-12-03 at 10.25.09 AM.png

Welcome to our 8th day of DevTest 8.0!  Today we are looking at the new CA Continuous Application Insight and it’s ability to Document Transactions.


First question who wants to document transactions - Boring!  Actually everyone does they just don't want to figure out what is behind the UI or API, the visibility created by CA Continuous Application Insight will allow you:


  • Create a system of record for what is behind the UI or API
  • Identify dependancies between application servers, databases, and 3rd-party services
  • Catalog Actual Interfaces used betwewen systems
  • Accelerate understanding of what is inherited form M&A
  • Document 3rd-party development of a system - architecture shift form white board


In the video for the 8th day of DevTest I show how you can run your manual test case and then get documentation generated based on your business transactions.  You can use this in development and training to demystify what is actually behind the system.





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 8th 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!"

--------------------------------------------------------------------------------------


ArpiJakab

The 12 days of 8.0 - Day 7

Posted by ArpiJakab Employee Dec 7, 2014

"On the 7th day of DevTest the CA team gave to me 7 well calibrated agents"


SIX agents, protocols, categories intercepted,

FIVE generated assets,

FOUR opaque data types processes,

THREE new execution modes,

TWO RR pairs added,

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


Welcome to the 7th day of DevTest 8.0! Today we are looking at the new CA Continuous Application Insight – specifically how to calibrate DevTest Java agents to capture the raw data that is turned into insights.

 

By default, agents do not capture transaction paths or transaction data. We call this zero-weight mode. In this mode, adding an agent to your application adds very little performance overhead – it also doesn’t capture transactions that can be used to generate virtual services or tests.


Unlike light-weight APM agents which only capture performance data – the DevTest agent captures transaction request/response payloads. A single transaction frame may be as large as 1 MB. Serializing each frame does add a run-time overhead. To minimize the performance overhead on your application, it is essential to properly calibrate each agent to only capture the data that is needed for visibility and for the generation of virtual services, baselines and documentation.


A well calibrated agent will produce fewer transactions, with less data. This means that you will require less storage to warehouse the data and won’t have to sift through a lot of captured noise when looking for transactions during CAI artifact generation.

Each agent is calibrated separately. This gives you maximum flexibility over what data you wish to capture. Each protocol supports three levels of data capture:

  • Counts – Capture only the number of invocations for this protocol type.
  • Counts and Paths – Include this protocol in the transaction path
  • Full Data – Include this protocol in the transaction path with full data request/response payloads 

 

For advanced users who are interested in POJO serialization. The Settings tab gives you full access to the agent’s transaction serialization settings. Settings.png


Some of you may have noticed that I've only calibrated only one agent, the other six are left as an exercise for you!


--------------------------------------------------------------------------------------

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!"

--------------------------------------------------------------------------------------


"On the 6th day of DevTest the CA team brought to me 6 more agents, protocols, categories intercepted


FIVE generated assets,

FOUR opaque data types processes,

THREE new execution modes,

TWO RR pairs added,

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


The new CA Continuous Application Insight is based on using our java agent technology to introspect your running business processes to find "live paths".  The way this works is we put our java agent into the start up of your application, usually via the JAVA_TOOL_OPTIONS, and point the agent to our CA CAI Broker and start your application.  When your application starts up you will see a message about the agent version, name, status, and remote broker connection.  Quietly in the background we will start to instrument your application looking for interesting transactions.  In general we look for:Screen Shot 2014-12-04 at 1.22.48 PM.png


  • Inbound http/s communications - web pages, web services, rest calls
  • Inbound socket communications - raw TCP/IP calls, java RMI or JNDI lookups, JMS messages, MQ Series
  • Outbound http/s communications - going out to another machine for data
  • Outbound socket communications - JDBC, TCP/IP, java RMI or JNDI lookups, JMS messages, MQ Series, plane old sockets with CTG or IMS connect
  • Inside the java virtual machine we see JDBC calls, EJB2, EJB3, IS flow services, Tibco activities


The agents start out a bit quiet and only track use counts which helps you identify what core components are being used, you can then dial up your transactions to see the counts and paths, or stitching of a business transaction into the live paths.  Getting the paths takes a little more work (CPU) by the agent and broker but the visibility gained is great.  The final thing you can do is turn on full payloads plus paths and you will get robust information about what is called and all of the data associated with it.  Great thing is you get full visibility, just remember to make sure you have enough DB space to store all the transaction so you can generate virtual services and baseline tests.


When there are extra or noisy transactions you can include them or exclude them.  For example, if your application has a heart beat between two servers, it is good to know it is there but can create tons of noise in the list of transactions in the CA Continuous Application Insight web user interface.  We allow you to right click and stop persisting the heartbeat or you can add a exclude clause to not even pay attention to the calls.  On the other hand if you have great custom frameworks written in your java that is just a bunch of POJO's you can explicitly include them into the paths to show more details so you can see your custom. 


Now that we have a basis of what the agent will capture what platforms do I put the agents into?  We test modern versions of J2EE and integration platforms running java 1.7, 1.6, and 1.5 (planned deprecation for 1.5 in next year). 


webMethods IS9.0, 9.5
Tibco BW5.10
JBoss4.2, 7.3
WebLogic10.3, 12.1.1 with Sun and JRocket JRE
Jetty

8, 9.1

WebSphere7, 8.5


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 6th 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!"

--------------------------------------------------------------------------------------


"On the 5th day of DevTest the CA team gave to me 5 generated assets


Four opaque data types processed

Three new execution modes,

Two RR pairs added,

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

 

 

Welcome to our 5th day of DevTest 8.0!  Today we are looking at the new CA Continuous Application Insight and it’s ability to generate Actionable Assets.


Screen Shot 2014-12-03 at 10.24.37 AM.png

What is a Actionable Asset? Actionable Assets are test cases, virtual services, and visibility documents into the business processes running behind the user interface and API’s based on live paths we observe in a running application.  On the 5th day of DevTest we specifically look at how to generate test cases (baselines) for API’s below the user interface.  If you think about that, simply you can now use a tool to automate your automation and get ahead of the curve for your automated regression testing. 


If you answer yes to any of these opportunities watch the video below.

 

  • “Don’t understand where the APIs are”CA CAI documents the transactions and show the API layer


  • “I enter data at the UI – I don’t understand data at the service layer”CA CAI baseline generation includes test data observed automatically


  • “I manually run the same test with different data”1,000’s of them – Automated test can be scheduled or integrate into CI / CD workflows

 

 

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 5th 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!"

--------------------------------------------------------------------------------------



"On the 4th day of 8.0 the CA Team gave to me,

FOUR opaque data types processed

THREE new execution modes

TWO RR pairs added

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

 

We have reached the 4th day of DevTest 8.0 and this gift is simply magic.  I explained a high-level description of Opaque Data Processing (ODP) in my blog before CA World on how it removes the need for the subject matter expert on new or unique protocols by using byte-level matching to find relationships in requests matching and response generation.

 

odp1.JPG

So today, let's get a bit more in depth on how Opaque Data Processing (ODP) works and what to use it for.


Service Virtualization Today and Its Challenges:

It all begins with how Service Virtualization works and something I like to call the DPH Challenge.  Service virtualization can be summed up in 3 steps: Capture, Process and Model

  1. Capture is the step where you gather the requests and matching responses in the virtual service.  Transactions can be captured in a few ways like inserting a pre-defined specification (WADL/WSDL), a set of log files/packet captures or even recording the transactions occurring on a live system,
  2. Process is the key to the puzzle.  It's what makes service virtualization something more than just stubbing and mocking.  In the process step, the protocol of the transactions is detected and CA Service Virtualization uses a Data Protocol Handler (DPH) to process the syntax and semantics of that data. Headers are identified, Operations and Arguments split out, de-identification is applied and business rules are identified (through magic strings/dates).
  3. Model is the final stage where the virtual service gets its routing steps.  This can be simple or complex but we'll leave that detail in the execution modes blog from yesterday.

 

Opaque Data Processing (ODP) addresses the "Process" step and solves "The DPH Challenge".  You see, the Data Protocol Handler is the brains of the operation.  Without it, the matching of requests and responses would be completely linear - one to one.  If there isn't an exact matching request in the virtual service, you do not get a response.  In order to build a DPH that can 'translate" the messages to find the best match, you must have a subject matter expert that can determine the syntax, semantics, and synchronization of the transactions. In many cases, with legacy technology or simply proprietary protocols, this Subject Matter Expert (SME) has left the company or simply doesn't exist.

 

The Magic:

odp2.JPG


ODP addresses the DPH Challenge by using patented algorithms to automatically find the relationships inside of nearly any data source, radically reducing the time required to create virtual services.  By using the Needleman-Wunsch genome sequencing alignment algorithm, ODP can discover byte-level patterns in messages and match those messages to the closest ones it has already seen before.  If we want to get technical, it calculates a distance function between the incoming request and a matching request to find which one most closely matches.  It also finds the matching bytes in the original request and response and duplicates that match in the newly seen request in the response it sends.  This is all the magic string functionality without having to parse the request.

 

 

Accuracy:

After this initial discovery, there we found two challenges within ODP. (1) The matching can be slow on a large data set and (2) the matching may not be completely accurate as it is not taking into account variability or invariability in the message.  For example, in a DPH, we would identify the "Operation" first and use that to find an initial match.  With ODP, and we miss that speed and accuracy.  Instead, every byte is equal.  To increase accuracy and speed of ODP, Entropy Weighting was born.  This is a technique that we coupled with ODP to be able to identify the bytes in a message that may be a header or an operation.  It strips out the headers due to high level of similarity with other messages and it identify s the operation as a set of bytes found 20-30 percent of the time (for example).  Then during matching, the first thing it will try is to find these similarities to match first (instead of the full string of bytes at once).  With this implementation we've found the following accuracy statistics on some already known protocols pushed through ODP:

odp3.JPG

Using ODP:

So at this point you're likely boggled by the complexity but excited for the true simplicity of this innovative replacement to the DPH.  You're likely asking yourself - "So where do I use this?" "How do I access it?" and "Why do I even need DPH's in the future?"

Let's start with this, ODP provides a turnkey solution to virtualize protocols otherwise not supported by CA Service Virtualization.  It's best used when you need reasonable data and you do not need to 'force" specific behavior (like negative test scenarios).

 

ODP doesn't work with encrypted messages (you'd have to decrypt first for us to find the sequence of bytes).  It doesn't detect stateful transactions nor does it support magic dates.  The content of the service image that is captured in the ODP process, is not often human readable and therefore you cannot easily edit that content unless you can translate EBCDIC off the top of your head.

 

With these circumstances, we feel there is clear use for DPH and clear use for ODP and will be keeping both technologies alive to both complement each other in addressing request matching and their coordinating responses.  Ideally, the future would allow us to take the matching/learned behavior from ODP and apply it to a more accurate, easier to read DPH with a few clicks!

 

The Simple Stuff:

Using ODP is a breeze, though it is not in the new DevTest Portal just yet.  Instead, you can access ODP under the "Transport Protocol" area in the 1st stage of recording a live virtual service in the DevTest Workstation (picture below):

odp6.JPG

 

Acknowledgements:

ODP is an exciting project to be a part of.  It not only was initially described as a "dream" by our team and now has become a reality but was developed by an up and coming PhD Candidate, Miao Du, from Swinburne University of Technology, Australia.  Just wanted to give a big thank you to the full team that contributed to defining the problem we wanted to solve, finding a solution (in the most unlikely area) and then getting this innovation into our product.  I hear they have more to come in the future as well!

odp4.JPG

 

Now that's my final gift to you from the CA Service Virtualization team.  Tomorrow I will hand the blogging reins over to the CA Continuous Application Insight team for the 5th day 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!"

--------------------------------------------------------------------------------------


"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

executionmodes.jpg


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!"

--------------------------------------------------------------------------------------


"On the second day of 8.0 the CA Team gave to me…

Two RR pairs added,

and a Server-Side recorder in a DevTest Tree"

(sung to the tune of the 12 days of Christmas)

 

Here we are at day 2 in our 12 days of DevTest blog series and I’m excited to share with you the highlights of our new virtual service editor in the CA Service Virtualization 8.0 DevTest Portal.

 

We’ve been told many times before that editing a virtual service in the good ol’ “LISA Workstation” was not for the faint of heart.  Alas, we’ve reinvented editing addressing the key feedback points from YOU our users.

editor.JPG

Since the blog is supposed to be focused on “Two RR pairs added”, let me start with that new feature and then move down the line on the rest of the amazingness in the new editor.

 

  • Two RR Pairs Added: Imagine, you just finished recording a virtual service and realized that the live service you recorded doesn’t have everything you need in that service image.  What to do?  Re-record is annoying and attempting to manually add the signature is painful.  Alas, we have a resolution – a simple plus sign allowing you to add Request/Response pairs by selecting or dragging and dropping the .xml or .txt files into the “add” window.  Talk about simplicity.
  • View Data on One Screen: Now what if you need to do a bit more with that service image.  Perhaps view the list of stateless transactions (signatures) and the request data (arguments and specifics) and response data in one screen?  Well in this new DevTest Portal, you can do just that.  No more scrolling pain or expanding windows that show ½ of what you need.  Now the key information on the requests and responses that are a part of your service image is available to you with a click of a button.
  • Conversation View: Although only a small set of virtual services are stateful, we felt it necessary to continue to share the tree/conversation view of transactions so that you can visualize dependencies as well as specific request and response data all in a single screen.  In addition, the ability to zoom into the conversation view or scroll around with the ‘finder’ helps with navigating large stateful virtual services.
  • Reorder Signatures, Arguments and Specifics: Now we’re getting to the meat of the service image – choosing the order in which requests are matched and responses are selected.  With the easy to use multi-select, drag and drop functionality you can move groups of Signatures, Arguments or Specifics with a few clicks. There are also nifty arrows to have you move items a few places along the scrollable list.  Now it’s easy to add more combinations to your virtual service to handle expanded coverage when in the testing phase of your application development.  All of this in a web-based user interface;  It’s stunning.
  • Open multiple service images from different projects: Sometimes features come as a side effect of good design.  The request to view the details of virtual services from multiple projects at once has come from many of our users.  It’s highly voted in our community as well.  Well with the new user interface in the DevTest Portal, you can select a project, select a virtual service, view its details and without closing it select another project, select a virtual service and view its details.  Now you can continue to use projects to delineate releases or teams but still enable assets from those projects to be viewed or worked on at the same time by the same user.
  • Searching with auto-fill and automatic drill into data found: Now we’re into the brains of the operation. One of the clear pain points of editing a virtual service is having to transverse through each specific transaction to find the area you want to edit.  The solution? Search.  But not just any search – smart search that automatically fills in suggested text as you begin typing based on the data it has indexed in your service image.  Intuitive search that automatically brings you to the specific content you were looking for and highlights the text so it’s clearly visible to the human eye. This isn’t just search, this is a game changer for those of you that need the ability to add business rules to your virtual service responses, create negative test scenarios from current, positive data or simply just find where a specific address is being referenced in a robust service image. (and yes, this works for conversations too)
  • Searchable Notes and Annotations: Another highly requested feature by our users, (here and here) the ability to add notes and/or annotations to your transactions, service image and even to the specific requests.  Folks have told us that they want to annotate a service image before handing it over to another team, so that transactions and specifics are clearly identified leaving less to human interpretation.  Maybe you want to identify a specific use case/test case, negative test scenario or a manually entered request or response.  You can now do so by adding a note to your Transaction or even editing the name of a Specific Request.  (No worries, we preserve the original name in case you ever need to see the operation name.)
  • Find a Match by Request: When asked why users need to edit a virtual service, over 75% of you stated that you want to see how the virtual service will respond to a specific request.  Well, the solution to this challenge all begins with your ability to search through the service image to find the information you need in a few clicks. With 8.0, you can paste request text or drag a request file into the ‘Find a Match by Request’ feature and swiftly find the match without the hassle of going over independent matching criteria.
  • Progressive Save: Same as in the server-side recorder, all changes you make in this editor are saved automatically to the service image.  No need to click “save” before you go to lunch. We’ll take care of that for you.

 

There are other hidden gems in this new virtual service editor, like

  • The confusing term “meta” has been changed to “default” to make it very clear which specific is the default or final match.
  • Some of the clearly advanced user features are hidden behind the advanced user interface toggle switch.  This keeps the UI clean for newer users but still gives our experienced users all the features they need.
  • Ability to format your response data to a more readable view as well as search within a specific response to get to the line you are looking for.
  • A right-click menu added to the “Manage” left navigation enabling you to (1) Easily deploy a virtual service, (2) Easily download an archive of the virtual service (MAR) for sharing outside of your team or (3) Delete that virtual service
  • Ability to link to a service image for sharing with your team.  Just grab the URL in your browsers address bar and send it to a friend.

 

Well that was a huge update and I’m still not sure if I captured all the greatness of this new Virtual Service Editor.  So much for just “Two RR Pairs Added”.

 

Check out this quick video to see our second 8.0 gift to you.

 


2nd Day of 8.0 - Open in YouTube

 

--------------------------------------------------------------------------------------

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!"

--------------------------------------------------------------------------------------


There is a lot going on lately in our community that I wanted to bring to your attention.

 

Let your voice be heard! Take the CA Service Virtualization Product Survey.

 

Your candid feedback is important to us and will help the CA Technologies Executive Management Team understand what is or is not working. The CA Service Virtualization (fka LISA) leadership team will also use the survey results to create action plans designed to further improve the overall experience and value you receive from your investment with us. The survey should only take 2-3 minutes to complete.


We have a fun new blog series launching today.  We have taken the liberty of renaming the “The 12 days of Christmas” song to “The 12 days of 8.0”.  Each day from Dec 1st through Dec 12th we’ll blog and video a demo of 1 key feature in 8.0.  If you are following along on Twitter use the hashtag #12daysofdevtest Here is the first post: http://bit.ly/12daysofDevTest-1

 

Ian Kelly’s Mobile Test Monday Blog Series was a hit. Enjoy all 9 posts here.

 

Who moved my LISA?!  The CA DevTest “Who moved my LISA?” campaign was a huge success with over 3500 views, 63 replies, 52 selfies and whole lot of fun.  The community is now officially called DevTest. Visit the blog post here to view the selfies. http://bit.ly/selfiewithLISA

 

Upcoming Events: Don't miss the CA DevTest Community Webcast on December 16 @ 11am ET.  The topic is: CA SV 8.0 Demo  CA Service Virtualization, CA Application Test, & CA Continuous Application Insight 8.0 has a set of great new features. We will demo them!  More info here: CA Service Virtualization 8.0 demo webcast on Dec 16 @ 11am ET

 

Member Spotlight Get to know our community members and CA staff with this monthly community member highlight:

 

Top Content this Week:

 

 

Polls are one of the ways we get your feedback quickly on a feature, function or decision we need to make on the product direction. If you have just a few minutes today, please respond to one or more of the polls on our community here and let your voice be heard!

 

There’s of course a lot more happening as well including Blogs, Ideas, Questions from users and more.

 

Contact me if you would like to contribute to the DevTest Community Blog or present during a webcast.  Members are invited to participate by sharing content that is interesting to the community.

 

Have a great one!

 

MaryGreening


The DevTest 8.0 release is almost here and leading up to it, we’ll be challenging our CA team in a fun, new way by asking them to get into the holiday spirit and sing their way through the 12 days of 8.0!

 

To kick us off, I’ll jump in with the first day of 8.0 (sung to the tune of the 12 days of Christmas)....

 

"On the first day of 8.0 the CA Team gave to me… a server-side recorder in a DevTest tree"


recorder1.JPG

Our new virtual service recorder in the DevTest Portal changes the way you think about creating a virtual service from an existing, live application.  Some of the highlights of the new recorder include:

 

  • Simplified Recording in 3 steps:  Record, Configure and Save your virtual service through our new DevTest Portal
  • Team Environment; No Individual Install Required: Install one copy of CA Service Virtualization on your server and grant your users access to the DevTest Portal to create new virtual services with ease. No need to install or manage upgrades on individual machines, instead, use a centralized service with access control for each team to share resources and collaborate on results.  Controls on access, virtual service names and ports used help handle any conflicts of the team environment.
  • Color Coded Status: As you move from field to field in the recording interface, the screen adapts to your inputs, showing you where to go next, which inputs are valid and which inputs need to be checked again before starting the recording.
  • Automatic Entry of Fields:  All you need is a name and the live backend service to get started.  CA Service Virtualization will select a free port on your VSE environment to both record and then deploy the virtual service.  In addition, error checking along the way will warn you when certain fields are filled in making it very simple to get from recording to deploying your virtual service in minutes.
  • Simplified SSL Configuration:  Recording secure transactions over SSL has never been easier. With certificate uploading into the recording screen, certificate and passcode validation and a visual representation of where the certificates reside, configuring your secure connection is a breeze.
  • Record, Edit and Deploy all-in-one Screen:  Complete the full virtual service workflow in a single user interface.  Create your virtual service with the live recorder, edit in the integrated virtual service editor and deploy right away.
  • Clear View into Transactions:  As you capture transactions in the recording, you can view them in real-time to see if the requests and responses you need to capture are getting through.  If you finish the recording but find that something was not done, simply go back and continue recording where you left off.
  • Add to a Recording: Not only can YOU add to a virtual service recording by continuing to record where you left off, YOUR TEAM can as well.  You can take a point-in-time copy of your recording and save it as a virtual service while your team continues to record additional transactions.  The recording files are still available on the VSE for anyone on the team to use and add to and redeploy without needing to start from the beginning again.
  • Progressive saving:  No worries if you forget to save your entries.  The new server-side recorder progressively saves your information as you type into each field.  Progressive save will save you, especially when you leave a recording to step away for lunch.
  • Automatic Protocol Detection: As usual, our automatic protocol detection will tell you which protocol we noticed in your live transactions so that you can apply the DPH and/or add other data protocol handlers to the virtual service with ease.
  • Advanced Mode: Advanced features of virtual service recording can be turned on with a click of a button.  This makes the default user interface clean and clear for newer users while still enabling our experienced users to get to the robust features of the live service recorder.

 

Check out this quick video to see our first 8.0 gift to you.

Enjoy!

 

The 12 days of 8.0 – Day 1 - YouTube

 

--------------------------------------------------------------------------------------

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!"

--------------------------------------------------------------------------------------