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

As CTO of Xebia and highly experienced in offshore testing in India, Guido articulates his methods in addressing common challenges faced by the in-house and offshore teams. He weighs heavily on strategic tactics as well as key cultural aspects to execute efficient and effective Agile methods. 1. I work at a US-based company and we ...
Testing in Agile Part 1 – INTRODUCTION TO AGILE In case you missed the first part of the series in our last magazine issue from Michael Hackett, Agile’s impact on software development teams is huge. For test teams it can be even more pronounced — and good, especially if your existing projects have been problematic.
LogiGear Magazine – November 2010
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 ...
Keeping an eye on the horizon in the testing world is an important part of staying in the game. Hans is no stranger to looking to the future with eyes wide and ears open. His expertise is what makes Hans valuable at the STARWEST Expo, which he recently delivered two talks to.
Build the right test platform including infrastructure, virtual lab and process. Testing embedded software is both similar and dissimilar to application software testing. The first eye-catching thing is that embedded software is significantly less visible to the end user. User interfaces are limited; there may be a console-based text menu, a simple command line interface, ...
Team collaboration is essential for testing embedded systems. Developing software for an embedded system often carries more risk than for general purpose computers, so testing is extremely critical. However, there still has to be a good balance between time spent on testing and time spent on development to keep the project on track. As consultants ...
Maximize the function of your teams The Modern Agile philosophy created by the folks at Industrial Logic is one of the most exciting ideas I’ve encountered in a while. Moving beyond the pre-canned “You must do X to be Agile” mindset that I’ve seen becoming more and more prevalent.
Writing code that is easy to read and easy to test is difficult to achieve. The fact that poorly written code can function often leads to coding practices that are effective but not necessarily efficient. Too often, many programmers fresh out of school write code in the manner that was effective for passing their courses, but contains ...
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 ...
When quality assurance teams and management who have adopted Agile practices first put the ideas to work, they face a significant impediment in unlearning the traditional mind-set and practices that experience in traditional practices has instilled in them. “He who knows to unlearn, learns best.” — Anonymous The following are some of the key aspects ...
Continuous Improvement and Short Feedback loops (think: Test Driven Development; Sprint Demo/Review; …) are at the core of any Agile process. Without a structured improvement process it can be difficult for teams to improve and without improvement we stagnate. For methods like Scrum, XP and et al., Retrospectives are that tool.

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe