Service Virtualization Rises to Cloud App Testing Challenge

One of the challenges with building an application these days is the number of dependencies that application will actually have on other applications. Ideally in order to know how that application will actually perform, application developers would be able to test their application against the application it depends on running in production. The odds of that happening, however, are slim to none, especially if that other application is running as a cloud service that has to be always available to end users.

To solve this problem developers are increasingly turning to service virtualization, which is an emerging set of application testing technologies that allows a developer to create a replica of another application in a testing environment. In fact, a recent survey of 200 in‐house software development executives and managers from enterprises with revenues of more than US $1 billion dollars in North America ‐ the majority (71%) with over $2 billion annual revenues – conducted by the market research firm Coleman Parkes Research on behalf of CA Technologies, found that not only does the inability to adequately test applications result in missed deadlines, entire functions wind up being eliminated and the development team as whole lacks confidence that the application will work as advertised.

Given the often limited scope of most application testing that may not be all that surprising. In fact, interest in agile development methodologies aside, as the amount of liability attached to an application increases the more cautious an organization becomes. What’s definitely needed, says Shridhar Mittal, general manager for service virtualization at CA Technologies, is a new approach to testing applications that for the most part are mashups of any number of existing applications that often have dramatically different service characteristics. The challenge, of course, is figuring which one of those applications might adversely affect the performance of your application before your application discovers that issue in a production environment, says Mittal.

Otherwise, says Mittal, all any organization is doing is releasing code on a little more than hope and a prayer that it will actually work.

As applications become increasingly borderless thanks mainly due to the proliferation of APIs that serve to make applications more accessible, the more tempting it becomes to invoke third-party APIs. But as we all know, the quality of APIs tends to vary widely across the Web. Right now many organizations are using agile development methodologies that in many instances amount to little more than trial and error when it comes to invoking APIs.As the number of application releases and updates that organization are rolling out in a given year steadily increases it’s pretty clear that existing approaches to testing applications won’t scale in the age of the cloud. Service virtualization provides a way to get around that scale issue that is not only practical, but more importantly should lead to better code being deployed the first time every time.

Originally published on ProgrammableWeb (programmableweb.com)

Michael Vizard
Michael is the Editor in Chief of InfoWorld Media Group where he has been covering computer technology for more than 14 years. He is also a member of the senior leadership team, which provides the strategic vision for InfoWorld Media Group.

The Related Post

LogiGear Magazine July 2012 Testing in Agile  
Agile, in terms of software development, has incorrectly and for too long come to mean fast and “getting product out the door quicker.” But Agile is not about speed; it is about being flexible. I always begin my discussions on Agile development by getting a definition for the word Agile. Agile, in terms of software development, ...
Author Jonathan Rasmusson explains in his latest book how to successfully set-up, execute and deliver Agile projects. Download the excerpt below for “Chapter 7: Estimation The Fine Art of Guessing.” To read his interview in last month’s issue, please click on “Spotlight Interview: Jonathan Rasmusson” to read his views on the best practices for test ...
If your Agile implementation is not about people, you’ve missed the boat! The most profound impact to becoming more Agile is happier teams! Agile manifesto Value #1: * Individuals and interactions over processes and tools Words like these do not show up in Waterfall or RUP SDLC process descriptions. Agile cannot get more basic than ...
Agile methods were developed as a response to the issues that waterfall and V-model methodologies had with defining requirements and delivering a product that turned out to be not what the end user actually wanted and needed. From www.agiletesting.com.au A software tester’s role in traditional software development methodology, a.k.a waterfall & the V-model can be ...
This article presents ten tips for Agile testing based on our experience. However, don’t expect to find the perfect test approach for your company or software project in this article. That is still something you will have to find out yourself! Several years ago I started as test manager on a J2EE project. The project ...
LogiGear Magazine – November 2010
Armed with the right tool or set of tools, a development team can incorporate ALM into its Agile process and start reaping the benefits of Agile ALM. As the software development industry matures, it is devising methods for ushering products from inception to completion—a process that has come to be known by the buzzword ALM ...
Agile is a philosophy focused on delivering constant value to customers incrementally and frequently, based on communication and feedback. These two ingredients are vital to a successful Agile recipe. Agile is no longer a buzzword or an unknown territory in the industry. Agile has progressed leaps and bounds the last few years and has matured to ...
How to fit automated testing into scrum, and keep testers in sync with other teams One of the benefits of the approaches of agile projects is their friendliness towards testing. The testing activities, and the testers with it, are integrated into the teams, and testing and quality are redefined as team responsibilities. Automation nowadays is a must-have ...
Janet Gregory draws from her own experience in helping agile teams address alternative ways to cope with roadblocks including projects without clear documentation, testers with limited domain knowledge and dealing with either black box or white box testing. For testing on projects without clear documentation, is exploratory the only method? I often make “tester errors” ...
This is part 2 of a 2-part article series; part 1 was featured in the September 2020 issue of the LogiGear Magazine, and you can check it out here. Part 1 discussed the mindset required for Agile, as well as explored the various quadrants of the Agile Testing Quadrants model. Part 2 will delve into ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe