Productivity: Testing

A week ago, we posted the results of an extensive survey that we conducted on the key factors for the success/failure of UI test automation pilot projects. The report that we produced based on the survey results created a lot of buzz in the community; it seems both testers and developers alike take a lot of interest in the subject, so we decided to organize a webinar as a follow-up to the survey report. We’ve invited two of the mavens in the testing field to help moderate this online discussion: Jim Holmes and Jim Evans.

We wanted to gain a better understanding of what it takes to be successful in the UI test automation field, so we can better guide our customers on a path to success with their automation projects. That’s why we decided to do this survey. Our goal was to explore the first steps teams in the field of automated functional testing take, as well as where they are today with their automation efforts and what helped them get there.

In our contact with organizations focused on delivering higher-quality solutions to customers, often we come across teams that struggle to build up their test automation proof of concept or, worse, fail to get on the right foot with UI test automation at all. Implementing test automation is a complex, intricate process

  The Telerik Test Studio team just got its third major for this year product update out the door. Test Studio R3 2014 is packed with excellent UI enhancements that help optimize your Test Studio real estate and minimize the steps needed to take to get your job done.

Even though Kendo UI makes it easy to build gorgeous UIs, teams regularly struggle with getting solid UI testing wrapped into their delivery flow. Teams often run into issues with asynchronous operations, difficult Document Object Model (DOM) structures, or browser incompatibilities that challenge team members writing functional UI tests.