Today we're happy to announce Test Studio R2 2013. This release brings changes to licensing and packaging, introducing our new monthly and annual subscriptions, as well as separate Functional and Load testing product bundles, making it easier for you to purchase just the product best suited for your project needs; Dan has a complete blog post on that. We're also bringing you several new features and enhancements: Earlier this year Test Studio introduced the new Test Recording surface - a JavaScript, KendoUI-based recording engine which enabled creation of tests using Chrome, FireFox and Safari. This release adds cross-browser improvements to ...

In Part 2 of the series on Telerik's Radcontrols for Windows Phone, we will continue adding several cloud-powered components such as RadCloudRegistration and the RadCloudCalendar control to the app.

Robert Pack asks I noticed from the first installment of the series that you say you write classes and methods so that they only just pass tests and no more, cutting down on dead code and zombie bugs. Where does this fit into some peoples’ rules for methods having a maximum number of lines etc? Do you think that’s a completely unrealistic limit to place on methods and that they will be as long as they have to be or do you subscribe to keeping methods below a certain size? I’m interested to hear your thoughts on this.

One of the key concepts when building an application stays the layout – what should it be? How should it be defined? It’s a tough question with lots of different answers. Of course, Telerik always tries to make the development easier and here is our answer as simple as possible – the combination of RadMenu and RadDocking controls.