Telerik Adds API Load Testing to Application Testing Tool

Michael Vizard
Dec. 12 2013, 11:00AM EST

There’s nothing quite as adventurous in all of IT as spending months building an application that depends on a third-party API for its success. For the most part, developers usually don’t know for sure how much stress the IT infrastructure supporting any given API can stand. If their application is wildly successful, it could suddenly slow to a crawl when that third-party API gets overwhelmed by requests.

To help developers identify what threshold of requests any given API might be able to withstand, Telerik this week released the latest upgrade to Test Studio, which includes the ability to simulate real-world user loads against a site or a web service.

According to Chris Eyhorn, executive vice president of the Application Lifecyle Management (ALM) division at Telerik, that load-testing capability can be used to model the point at which any given number of users might degrade the performance of a particular API.

In addition to load-testing capabilities, Telerik includes the capability to fully record sessions in all browsers to better facilitate testing of applications that will be accessed by multiple browsers.

Related Searches From ProgrammableWeb's

Directory of More Than 10,000 APIs

Browse The Full Directory

To make the Telerik testing tool more financially appealing, Telerik this week also implemented some new pricing options. Developers can now opt to download Test Studio and run it locally, but pay for it on a monthly usage basis. Eyhorn says this not only makes Test Studio more affordable, but it allows developers to only pay for testing software when they are actually using it. Of course, Telerik will continue to offer existing annual and perpetual licensing options. But Eyhorn says this new licensing option should make subscribing to testing tools more appealing to smaller teams of developers that have limited budget resources.

With the rise of agile development application testing is getting the short shrift more often these days. Developers are under more pressure to deliver applications faster, which almost invariably results in testing short cuts. By making testing tools more accessible, Eyhorn says it’s more likely that developers will avail themselves of a testing process that can eliminate some very costly fixes to production applications later on.

Of course, there’s no shortage of application testing tools these days inside and out of the cloud. Eyhorn says most developers still prefer to test locally because it allows them to work without having to always have an Internet connection while at the same time do a better job of actually replicating the end user experience. As for open source tools, Eyhorn says they are not only time-consuming to set up, but they also typically don’t provide as comprehensive testing environment.

Regardless of the approach taken, testing can be the difference between success and failure, especially in a world where any application is only as good as its weakest API link. The challenge is finding a way of reducing the cost of application testing that already consumes a fair amount of the typical IT budget.

Michael Vizard

Comments