Today we're happy to announce a new release of Icenium with a number of new features, updated library support, and stability improvements. There's a lot to cover so let's dive right in.
It’s been 2 years, 4 months, and 28 days since my last blog post – so I figured this one had better be good.
Over the past several years, the team at Telerik has shipped countless new features evolving Test Studio from an automated testing tool to an end-to-end testing solution. While the focus has always been and will remain on end to end testing – we’ve decided to split our offering into two solutions – one focused on functional test automation, and one focused on load testing. For those who want it all – fear not, we will continue ...
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.
Many sites and web applications are using iframe elements to create tabs or sections on the page which the user can enable/disable/move at will. These often are being created in such a way that putting an ID on each frame is difficult or not feasible. As each frame is created or destroyed, of course, the index of a given frame within the frames collection changes. These factors combine, making it very difficult for an automation framework to reliably locate elements within the frames. Beginning with the R2 release, Test Studio 2013 introduces Custom Tags for Frames, a way to ...
Adam Hall asks
Just a quick question regarding TDD, encapsulation and DateTime.Now()
I’ve often seen suggestions that you should control the behavior of DateTime.Now so that you can reliably test the way classes react to date times.
Controlling DateTime is a solution, but it smells of violating encapsulation, you are affecting objects from outside of their boundaries (and indeed system wide)
In your experience what is the best way to deal with Dates in TDD?