Monday, April 22, 2013

Service Virtualization brings speed benefit and lower costs to TTNET applications testing

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy. Sponsor: HP.

Welcome to the latest edition of the HP Discover Performance Podcast Series. Our next discussion examines how TTNET, the largest internet service provider in Turkey, with six million subscribers, significantly improved applications deployment while cutting costs and time to delivery.

We'll hear how TTNET deployed advanced Service Virtualization (SV) solutions to automate end-to-end test cases, gaining a path to integrated Unified Functional Testing (UFT).

To learn how, we're joined by Hasan Yükselten, Test and Release Manager at TTNET, which is a subsidiary of Türk Telekom, based in Istanbul. The interview is conducted by Dana Gardner, Principal Analyst at Interarbor Solutions. [Disclosure: HP is a sponsor of this and other BriefingsDirect podcasts.]

Here are some excerpts:
Gardner: What was the situation there before you became more automated, before you started to use more software tools?

Yükselten: We're the leading ISP in Turkey. We deploy more than 200 applications per year, and we have to provide better and faster services to our customers every week, every month. Before HP SV, we had to use the other test infrastructures in our test cases.

Yükselten
We mostly had problems on issues such as the accessibility, authorization, downtime, and private data for reaching the other third-party’s infrastructures. So, we needed virtualization on our test systems, and we needed automation for getting fast deployment to make the release time shorter. And of course, we needed to reduce our cost. So, we decided to solve the problems by implementing SV.

Gardner: How did you move from where you were to where you wanted to be?

Yükselten: Before SV, we couldn’t do automation, since the other parties are in discrete locations and it was difficult to reach the other systems. We could automate functional test cases, but for end-to-end test cases, it was impossible to do automation.

First, we implemented SV for virtualizing the other systems, and we put SV between our infrastructure and the third-party infrastructure. We learned the requests and responses and then could use SV instead of the other party infrastructure.

Automation tools

After this, we could also use automation tools. We managed to use automation tools via integrating Unified Functional Testing (UFT) and SV tools, and now we can run automation test cases and end-to-end test cases on SV.

We started to use SV in our test systems first. When we saw the success, we decided to implement SV for the development systems also.
Gardner: Give me a sense of the type of applications we’re talking about.

Yükselten: We are mostly working on customer relationship management (CRM) applications. We deploy more than 200 applications per year and we have more than six million customers. We have to offer new campaigns and make some transformations for new customers, etc.

We have to save all the informations, and while saving the information, we also interact the other systems, for example the National Identity System, through telecom systems, public switched telephone network (PSTN) systems.

We have to ask informations and we need make some requests to the other systems. So, we need to use all the other systems in our CRM systems. And we also have internet protocol television (IPTV) products, value added services products, and the company products. But basically, we’re using CRM systems for our development and for our systems.

Gardner: So clearly, these are mission-critical applications essential to your business, your growth, and your ability to compete in your market.

Yükselten: If there is a mistake, a big error in our system, the next day, we cannot sell anything. We cannot do anything all over Turkey.

Gardner: Let's talk a bit about the adoption of SV. What you actually have in place so far?

Yükselten: Actually, it was very easy to adopt these products into our system, because including proof of concept (PoC), we could use this tool in six weeks. We spent first two weeks for the PoC and after four weeks, we managed to use the tool.

Easy to implement

For the first six weeks, we could use SV for 45 percent of end-to-end test cases. In 10 weeks, 95 percent of our test cases could be run on SV. It was very easy to implement. After that, we also implemented two other SVs in our other systems. So, we're now using three SV systems. One is for development, one is just for the campaigns, and one is for the E2E tests.

HP Software helped us so much, especially R&D. HP Turkey helped us, because we were also using application lifecycle management (ALM) tools before SV. We were using QTP LoadRunners, Quality Center, etc., so we had a good relation with HP Software.
Since SV is a new tool, we needed a lot of customization for our needs, and HP Software was always with us. They were very quick to answer our questions and to return for our development needs. We managed to use the tool in six weeks, because of HP’s Rapid Solutions.

Gardner: My understanding is that you have something on the order of 150 services. You use 50 regularly, but you're able to then spin up and use others on a more ad-hoc basis. Why is it important for you to have that kind of flexibility and agility?
We virtualized all the web services, but we use just what we need in our test cases. 

Yükselten: We virtualized more than 150 services, but we use 48 of them actively. We use these portions of the service because we virtualized our third-party infrastructures for our needs. For example, we virtualized all the other CRM systems, but we don’t need all of them. In gateway remote, you can simulate all the other web services totally. So, we virtualized all the web services, but we use just what we need in our test cases.

In three months we got the investment back actually, maybe shorter than three months. It could have been two and half months. For example, for the campaign test cases, we gained 100 percent of efficiency. Before HP, we could run just seven campaigns in a month, but after HP, we managed to run 14 campaigns in a month.
We gained 100 percent efficiency and three man-months in this way, because three test engineers were working on campaigns like this. For another example, last month we got the metrics and we saw that we had a total blockage for seven days, so that was 21 working days for March. We saved 33 percent of our manpower with SV and there are 20 test engineers working on it. We gained 140 man-months last month.

For our basic test scenarios, we could run all test cases in 112 hours. After SV, we managed to run it in 54 hours. So we gained 100 percent efficiency in that area and also managed to do automation for the campaign test cases. We managed to automate 52 percent of our campaign test cases, and this meant a very big efficiency for us. Totally, we saved more than $50,000 per month.

Broader applications

Gardner: Do you expect now to be able to take this to a larger set of applications across Türk Telekom?

Yükselten: Yes. Türk Telekom licenses these tools and started to use these tools in their test service to get this efficiency for those systems. We have a branch company called AVEA, and they also want to use this tool. After our getting this efficiency, many companies want to use this virtualization. Eight companies visited us in Turkey to get our experiences on this tool. Many companies want this and want to use this tool in their test systems.

Gardner: Do you have any advice for other organizations like those you've been describing, now that you have done this? Any recommendations on what you would advise others that might help them improve on how they do it?

Yükselten: Companies must know their needs first. For example, in our company, we have three blockage systems for third parties and the other systems don't change everyday. So it was easy to implement SV in our systems and virtualize the other systems. We don’t need to do virtualization day by day, because the other systems don't change every day.

Once a month, we consult and change our systems, update our web services on SV, and this is enough for us. But if the other party's systems changes day by day or frequently, it may be difficult to do virtualization every day.
Companies should think automation besides virtualization. This is also a very efficient aspect, so this must be also considered while making virtualization.

This is an important point. Companies should think automation besides virtualization. This is also a very efficient aspect, so this must be also considered while making virtualization.

We started to use UFT with integrating SV. As I told you, we managed to automate 52 percent of our campaign test cases so far. So we would like to go on and try to automate more test cases, our end-to-end test cases, the basic scenarios, and other systems.
Our first goal is doing more automation with SV and UFT and the other is using SV in development sites. We plan to find early defects in development sites and getting more quality products into the test.

Rapid deployment

Of course, in this way, we get rapid deployment and we make shorter release times because the product will have more quality. Using performance test and SV also helps us on performance. We use HP LoadRunner for our performance test cases. We have three goals now, and the last one is using SV with integrating LoadRunner.

Gardner: Well, it's really impressive. It sounds as if you put in place the technologies that will allow you to move very rapidly, to even a larger payback. So congratulations on that. Gain more insights and information on the best of IT Performance Management at www.hp.com/go/discoverperformance. And you can always access this and other episodes in our HP Discover performance podcast series on iTunes under BriefingsDirect.
Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy. Sponsor: HP.

You may also be interested in:

Rush to enable enterprise mobile development pits native against container approaches

Both enterprises and independent software vendors (ISVs) know the software-development game's changed. Not only do they need to rapidly develop and deploy more mobile apps across multiple interfaces and device platforms, but they need to really rethink all of their client development -- and even try and come up with a singular approach to most of them.

Fast to their rescue, the suppliers of development tools and testing systems are tripping over each other to appeal to them in this new game. And as in the past with other deployment advances, we're seeing a major philosophical split between the "nativists" (running directly on the device hardware) and the "virtualizers" (with their scripting and interpretive layers and containers).

First, the nativists. Embarcadero Technologies, with its RAD Studio and former Borland CodeGear assets, is not surprisingly catering to its skills base -- the hard core developers at home in Delphi and C++Builder, as well as C and Objective-C. Embarcadero therefore today delivered RAD Studio XE4, with an attractive offer to those seeking native -- what Embarcadero calls "multi-device, true native" -- apps development, but across most mobile devices from a singular code base and a single core skills set. RAD Studio XE4 has a single application framework for iOS, Windows, and Mac OSX, with support for Android coming soon.
But native development for mobile (nee PCs) isn't the only game in town, nor the only way to seek the "run anywhere" nirvana.

RAD Studio XE4 allows developers to gain more control over the development lifecycle and deliver apps with tighter security, a better user experience, lightning quick performance, and a small footprint. Those that want to target iOS devices, as well as OSX and Windows PCs, can write once and run anywhere, so to speak, says Embarcadero. The key is FireMonkey, a cross-platform GUI framework developed by Embarcadero to provide Delphi and C++Builders with a single framework. This is the same lineage of the graphical language tools that sprung from native (fat) PC development.

But native development for mobile (nee PCs) isn't the only game in town, nor the only way to seek the "run anywhere" nirvana. The other approaches to the mobile and cross-platform development complexity problem are more aligned with open source, HTML5, and scripting, all with roots in the web.

And so HP last month, threw it's weight from the IT management perspective behind "a hybrid approach" for mobile. HP Anywhere, as HP calls it, aids in the distributing and consuming of IT management information to mobile devices. But this may well be a model for far broader enterprise-to-mobile process alignment.

Especially where BYOD is the goal, the hybrid approach works best, says Genefa Murphy, Director of Mobile Product Management and User Experience at HP Software. [Disclosure: Both Embarcadero and HP are sponsors of BriefingsDirect podcasts.]

Under this "virtualizers" vision, the HP Anywhere server connects IT management systems to the HP Anywhere Client on Android or iOS devices, forming the basic client app or container on the end-point devices. Then so-called Mini-Apps are downloadable to that container to provide the access and interface to specific IT management tasks or modules.

Two best ends

These two examples of mobile enablement to me represent the two best ends of the enterprise mobile needs spectrum. And chances are, enterprises are going to need both, especially for existing applications and processes. For example, the Embarcadero approach can swiftly take existing full-client applications and deliver them to the needed mobile tier devices with strong performance and security, and no need to rewrite for each client and OS, said John Thomas (JT), Director of Product Management at Embarcadero.

For more on my views of how cloud, mobile and enterprise IT intersect, see my two-part interview on the Gathering Clouds blog.

The question yet to be answered is what combination of native, scripting, or hybrid container-type models will fit best for entirely new "mobile first" applications. This is a work in progress, and will also vary greatly from company to company, based on a maze of variables for each. Looks for a lot more blogs on that greenfield apps trend in the future.

For now, however, a lot of the pain for IT in going mobile is in getting existing PC applications via code reuse -- as well as business processes on back-end systems -- out to where they can be used . . . on the modern mobile landscape and in the hands of newly empowered mobile users. Incidentally, the new Embarcadero tools and framework allows .NET apps to be driven out to iOS devices in a pretty snappy fashion. That's assuming, of course, Windows CE won't be your preferred client environment after all. You know who you are.

Currently, RAD Studio XE4 delivers multi-device development for ARM and Intel devices, including Apple iPhone, iPod Touch, iPad, Mac OSX, Windows PCs, Slates, and Surface Pro tablets, said JT. And RAD Studio XE4 allows developers to take advantage of the full range of capabilities available on each of those devices to deliver the best user experience, he added. The full Android support should come mid-year.
The Embarcadero tools allow developers or designers to also quickly create no-code, visual mockups with live or simulated data and deploy to actual target devices

The Embarcadero tools allow developers or designers to also quickly create no-code, visual mockups with live or simulated data and deploy to actual target devices (like PCs, phones, or tablets), or simulate on Windows or Mac, so that the requirements and app role can be best defined and tuned.

RAD Studio XE4 is available immediately. To download a free trial, visit http://www.embarcadero.com/products/rad-studio/downloads. Pricing starts at $1,799. Delphi and C++Builder pricing starts at $149 for Starter edition and $999 and up for full commercial development licenses. Upgrade discounts are available for users of recent earlier versions. An introductory 10 percent discount is available on most RAD Studio XE4 family products through May 22.

As for HP Anywhere, it manages the cross-platform device client issue using HMTL5 and Javascipt, and we'll be seeing a lot of that too from many "virtualizers." HP also boats RAD via an emulator that allows quick switching between device views. HP is taking its HP Anywhere story to both the test and QA people as well as developers as they seek ways to bring more business functions to the mobile enterprise worker corps.

You may also be interested in: