How one ISP used service virtualization to deliver apps faster and cut costs

aw-tendo-glam.jpg

I’ve written about how automation and unification speed up the testing process in the abstract before, but I recently listened to a podcast that serves as an interesting, real-life example.

 

In the podcast, Dana Gardner, principal analyst at Interarbor Solutions, interviews Hasan Yükselten, test and release manager at TTNET, a subsidiary of Türk Telekom based in Istanbul. TTNET —Turkey’s largest Internet service provider, with about 6 million subscribers — faced the same challenge many HP customers do with their application development.

 

TTNET was deploying more than 200 applications annually, but to keep and exceed that pace they needed to get more efficient at testing. The problem: They couldn’t automate testing because parts of their system were on third-party infrastructures. The solution they turned to was service virtualization, which abstracts the service from the underlying hardware, making it possible to test and develop applications faster.

 

The quickening pace of app dev

As the speed of development accelerates, dev teams must pick up the pace and follow agile practices to keep up with the competition.

 

TTNET was having problems with accessibility, authorization, downtime, and private data when reaching into third-party infrastructures. Before adopting HP Service Virtualization, TTNET couldn’t do automation.

 

“We needed virtualization on our test systems,” Yükselten explains, “and we needed automation for getting fast deployment to make the release time shorter. And of course, we needed to reduce our cost.”

 

Mission-critical CRM

Most of the apps TTNET deploys enable customer relationship management (CRM). “We have to offer new campaigns and make some transformations for new customers,” Yükselten explains. So these applications are mission critical.

 

To get started, TTNET first virtualized internal systems, then used HP SV to connect its infrastructure with third-party infrastructures. “We learned the requests and responses and then could use SV instead of the other party infrastructure,” Yükselten says. “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.”

 

The benefits of automation and unification

TTNET’s story is not uncommon. HP research indicates that automation and unification speed up the testing process without compromising quality—and has some impressive numbers to back up that assertion:

 

  • 65 percent of IT organizations realized over 2 times ROI by automating testing with HP
  • Clients have reduced test cycle time by at least 25 percent
  • 70 percent of IT organizations are able to design tests in half the time
  • Clients have reduced their amount of regression testers in half

 

To get the full story on TTNET, download the podcast or read excerpts at Dana Gardner’s BriefingsDirect blog.

 

Related links

Best practices: Implementing automated functional testing

How automation and unification speed up the testing process—without sacrificing quality

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
About the Author
Alec Wagner is a longtime writer & editor, enterprise IT insider, and (generally) fearless digital nomad.


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation