Skip navigation
All Places > DevTest Community > Blog > Authors ArpiJakab

DevTest Community

5 Posts authored by: ArpiJakab Employee

We are pleased to announce that the DevTest 8.5 is generally available (GA) as of October 8, 2015.  This release includes both fixes to reported issues as well as enhancements to our 3 core products based on customer feedback and ideas.

The DevTest suite includes v8.5 of products:

  • CA Service Virtualization
  • CA Application Test
  • CA Continuous Application Insight (CAI)



CA Service Virtualization

  • New TCP/IP recorder in the DevTest Portal. This is our first of many new recorders in the portal!  Specifically you can record TCP/IP traffic and create virtual service from the DevTest Portal.
  • HATEOAS support for creating HTTP REST virtual services. Parse URI parameters according to RFC 3986 --  extract metadata from URI parameters instead of truncating the URI.
  • Monitor virtual services and recordings from the DevTest Portal.  Amazing new UI to view your Virtual Services, with ability to multi select and act (change state, think time, etc) with NEW sorting and filters to find your services quickly.
  • Find and Replace functionality in the DevTest Portal. Added the ability to find data in a service image and replace that data within a few clicks.


CA Continuous Application Insight

  • New application services insights. Let CA Continuous Application Insight find your common API's consumed by multiple applications and build valuable regression tests and virtual services.  The identifying of common API's means that we are finding the expected behavior of multiple  consumers at once.
  • Enhancements to PDF reports.
    • Show merged paths information.
    • Show agent boundaries for transaction graphs.
  • Deploy Java Agent from DevTest Portal. This solves the pain of copying the Java Agent file between machines during agent install.

CA Application Test for Mobile

  • New support for testing mobile browsers.  Many applications on mobile devices are purpose formatted web sites, you can now test these web sites running in Safari or Chrome on your mobile device.
  • Graphical simple creation of XPath expressions.  When editing a mobile test you can now view the page source with easy graphical view and we create your XPATH expressions via point and click.  This will make creating assertions and filters dramatically easier and faster.
  • Easier configuration device and lab setup.  In 8.5 you can point your test case to different devices and labs for execution via new dialog vs. correlating to asset.  The pointer to device and lab is now saved in your default or alternate configuration so changing were you want to run your tests is as easy as selecting a alternate config just like you do for all of your CA Application Tests  


Documentation: The full release notes are available here Release Information - DevTest Solutions - 8.5 - CA Technologies Documentation

CA World 2014 is now a distant memory, although one keynote really stuck with me. Chris Satchell is the Consumer Technology Officer at Nike. Chris made the statement that “everyone is an athlete”. Anecdotally this statement did not ring true to my ears. My fitness goals mainly revolve around early heart attach prevention – less so around what is generally considered athleticism. So I mentally geared up to dismiss Chris’ comment under the general label of marketing mumbo-jumbo.

As Chris kept sharing his Nike philosophy and the technology they were creating; I was suddenly struck by the idea that Chris and other Nike employees really believe that I, the buyer of their shoe, will indeed “do it”. My inner athlete will emerge through Nike's partnership we me


Nike created a NIKE+ Running app to track distance, pace, time and calories. They have also created a NIKE+ Coach app to help customers “set and achieve your training and race day goals through customized programs designed for all experience levels”. My perception of Nike changed from a company that sells shoes to a company that is in the business of coaching athletes – that also happens to sell athletic apparel.

DevOps shoes1.png

Like Nike, CA technologies is also not in the business of selling products. CA’s customers want and need a true partnership with CA to achieve their DevOps goals. This partnership starts with meeting each individual customer at their unique stage of DevOps adoption.

The best athletes have the best coaches. At CA we are DevOps experts we coach each customer individually to set realistic DevOps goals and guide them in their product selections when executing their DevOps strategy.


In the application economy, every company is running a race against the competition. The companies with the fastest release cycles will come out ahead. Buying CA products will not instantly make you a top-performing DevOps athlete – just as buying a Nike shoe doesn't instantly make you lose 10 pounds or turn you into an NBA point-guard.

The successful DevOps athletes get off the couch of annual or semi-annual releases, set some achievable goals, deploy the right products and services, grunt through the initial pains of DevOps adoption, measure every aspect of their release cycle.

CA is the expert partner who coaches DevOps athletes to reach their potential.


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



Magic at CA World 2014

Posted by ArpiJakab Employee Nov 14, 2014

Earvin “Magic” Johnson was the Monday night keynote speaker. About 4000 mobile devices in the audience tried to capture “the magic”. He graciously walked up and down each isle from the front to very back – he gave attendees plenty of opportunities for close-ups and dozens of selfies. I consider myself restrained when it comes to fawning celebrities, yet I couldn't resist snapping a few photos as he made the rounds.

Magic is more than a nickname. The name was bestowed upon Earvin by a sportswriter when Earvin was only 15 years old. Over the next 40 years, Earvin cultivated the name into his own personal brand. Behind Magic’s warm personality and jovial character there is a mind of a warrior. Like Alexander the Great, Magic consistently finds a way to win in sports and in business for himself, for his team and for his community.


In his junior year at Everett High School, at the age of 14, Magic took his last place in standing team to the championship and win! He is the only one to ever win MVP in the NBA Finals in his junior year. He turned his $18 million earnings from his sport career to business holdings worth $500 million today. His foundation has provided 10000 scholarships for urban college students.



Behind the seemingly magical ease of his success, there is a lot of hard work, discipline and a keen intellect. As John Maxwell said “champions are not made in the ring they are merely recognized there”. During the keynote Magic shared some of the key components of his recipe for winning. When he joined his high school team, he showed up every day at 7 am for practice, three hours before his teammates. When the coach found out, he forced the whole team to do the same. In the NBA, he learned that his competitor Larry Bird was shooting 1000 shots a day in practice, so he also practiced just as hard. He studied his teammates, knew their strengths and weaknesses, knew if they were on their game by studying them in the locker room before the game. Like a general, Magic knows how to train himself and to lead his team to overcome specific opponents and situations.


In business he executes SWOT analysis on his businesses twice a year and before any new big change. A consistent winning streak is never an accident. He knows what is required to win and he prepares himself and his team to win. I particularly enjoyed his recipe for winning customers. In the early days of Starbucks, Magic opened more than a hundred Starbucks stores in urban communities. He replaced the usual elevator music with R&B and he added more sugary drink as is the preference of the African-American and Latino-American communities.


In his words, you have to know your customer and you have to over-deliver to them on your commitments. Sounds like a pretty good recipe for building good relationships.


Magic at 55 years old is still working on his game. Two years ago he made 28 three pointers in a row at a charity event against his arch rival Larry Bird. He still gets up at 4 am every day and hits the gym. He showed up two hours early for the keynote.


The last nugget that really impressed me was during the Q&A session of the keynote. Magic commented that when he first joined the Lakers, “it was Kareem’s team, although I ran it”. He was talking about the official team captain being Kareem Abdul-Jabbar, yet he made sure to lead the team even without the title of captain. The big takeaway for me was that regardless of our title, we should all look for opportunities to lead ourselves, our team and our company to victory.

It’s a completely inappropriate children’s book title, but fitting for enterprise software.


My code is my baby—I’ve conceived it. I’ve even nurtured it through sleepless nights. I want it to grow up and play nicely with others. When it runs around in my dev environment, it behaves perfectly. However, when it goes off to the testing environment, the trouble starts. I start hearing stories of misbehavior and admittedly, I’m quite incredulous. How can it be? I know every single line of this code and I’ve tested it locally; I know it works. Earlier in my career, I may have even cast a few askance looks at my QA colleagues who badmouthed my baby. I was in denial.


Over the years, with some resignation, I have faced the fact -- my baby behaves differently when it’s not home -- and this is BAD! But what can I do? It’s all grown up and out the door, hanging out in strange new environments with testing folks who are paid to give my code a hard time. As I struggled to recreate the testing environment and steps to reproduce the bugs, I was failing to deliver on stories that I had committed to at the beginning of the sprint.


Brace yourself... here is my pitch for a more pleasant and productive way to write software.


Step 1 - Ask your operations folks to attach a CA Path Finder agent to each application server in your staging environment.

Step 2 - Write and test, business as usual.

Step 3 - A business transaction failed or is reported slow in the test environment, a.k.a. bizarro world. No problem, open up the CA Path Finder web UI and lookup the failed transaction. Examine the details of each captured call and trace the details of the failed business transaction through all the tiers of the application. Use Path Finder to examine exceptions and to log messages both in the context of a business transaction path.

Step 4  Fix the bug, move on to other stories and finish the sprint strong!



You may be thinking -- sure this will work for some bugs, but what about mandelbugs and heisenbugs? True, we have a debugger for a reason: some bugs are tough and need heavy duty root cause analysis. There may not be enough details in the captured business transaction details to deduce the exact cause of the bug. With a few extra steps you can use Path Finder to generate a test that you can use to reproduce the bug in your code on your dev box. Your code depends on backend systems -- if these are not available, use Path Finder to generate virtual services to fill in for the unavailable backend systems. You have your app and the virtual services running, attach the debugger, run the test and debug as usual.

As developers we can’t anticipate and test every scenario our code will experience in the wild.  A more productive use of time is to precisely monitor how code behaves differently in other environments. With Path Finder, you can be more involved in your code’s upbringing.