We’re taking a new step for Test Studio: we’re making Test Studio 2013 R1 available as a public beta. This release of Test Studio has undergone some major changes, and we’d like your feedback on what you think of things so far!

We’re making a Beta build of R1 available for you until 15 August. The Beta will expire at that point, so keep reading if you’re interested in having an early look at the release!

Where to Get It

We’ve made the Beta build available right on your Telerik.com My Account page. (Don’t have an account? All you need to do is register at Telerik.com. You don’t need to purchase anything, sign up for newsletters, or hand us over your firstborn.)

Where to Read More

Part of our Beta program is allowing you access to our early draft documentation. We’re trying to make sure our documentation is clear, complete, and helpful. Let us know where we can continue to flesh things out for you.

What We’d Like From You

Test Studio 2013 R1 is a significant change from earlier versions. You’ll see a completely new theme for the UI, you’ll find more features, and you’ll be able to record in more browsers. Here are some of the things we’d love to hear back from you on:

• What do you think of the new UI?
• How is Test Studio’s performance, especially in large projects, working for you?
• What do you think of the new recorders in Chrome, Safari, and Firefox?
• How is the new distributed execution environment working for you?
• What’s unclear?
• What’s not working?
• Are you having any problems installing?
• Any problems upgrading and using existing projects?

Don’t feel constrained by the list above. Let us know whatever feedback you’ve got!

Where to File Feedback

We’ve created a special portal just for this Beta. Please fire away with bug reports, feature requests, and feedback there.

Disclaimer

This is a Beta release, folks. Please do not install or use this in your production environments. We may still make breaking changes to the product, and we don’t want you to paint yourself into a corner. This also means you shouldn’t be checking in any changes you make with this Beta to your main test projects in source control. (Not using source control for your test projects? Please, stop reading and go get it set up. I’ll wait here.)

About the author

Jim Holmes

Jim Holmes has around 25 years IT experience. He's a blogger and is the Director of Engineering for Telerik’s Test Studio, an awesome set of tools to help teams deliver better software. He is co-author of "Windows Developer Power Tools" and Chief Cat Herder of the CodeMash Conference. Find him as @aJimHolmes on Twitter.

Interested in chatting with Jim at a conference? Check out his speaking schedule!