A few months back our announcement of Fiddler joining the Telerik family received huge response in the community. As part of our efforts, we made it a point to ask you for advice and feedback on next steps. Much like the news itself, this request was well received and funneled back to us amazing, interesting and very useful feedback and advice. The impact of the community has helped us stay focused and devoted to the thousands of Fiddler users, and deliver on our promise to provide better user experience, support resources and additional product features in the months to follow. ...

I wanted to personally thank the entire Fiddler community for the overwhelming response to last week’s announcement that Telerik has acquired Fiddler. The feedback has been just amazing – in just a week Twitter has absolutely blown up and our survey asking for your input has already received more than 1400 responses (keep an eye out for a future post based on those responses)!

If it wasn’t obvious before just how important Fiddler is to the community, here a few or my personal favorites.  But don’t take my word for it, feel free to see the Tweets for yourself or read ...

We have some very exciting news to share with the Telerik community.  Telerik has just acquired Fiddler!  Even more exciting is that Fiddler’s brilliant creator Eric Lawrence will come over from Microsoft to join the team fulltime.  For those of you who don’t know, Fiddler is a web debugging proxy which logs all HTTP(S) traffic between your computer or device and the Internet. In other words, it is an essential tool for any web, desktop or mobile developer.  The popularity and sophistication of Fiddler is hugely impressive considering this has been Eric's informal side project for more than 8 years.  With Eric joining the team ...

The rise and impact of automated testing tools and technology

The year was 1962 and the world was catching its first glimpse of the daring and colorful wonders that tomorrow might bring. It was a space-age vision of a technology-filled future – flying cars that could fold down into an attaché case, wisecracking robotic maids, and miraculous machines that could do anything from washing the dog to cooking a three-course gourmet meal, all at the touch of a button. It was a utopian society made cleaner, better, and more prosperous through the auspicious use of technology and automation.

This description, ...

It is hard to believe that January is already behind us as we dive deeper into 2011. For the testing tools we saw an amazing year of product growth and innovation and I would like to share with you some big announcements from the testing tools division for the upcoming year.

The first big announcement is that we are going to have two major releases a year for Telerik automated testing tools in order to focus more on new product development and new feature development. The R1 release will be around the end of April and the R2 release will ...

One of the great new features in the Q2 release of WebUI Test Studio is the ability to record and execute tests using Silverlight’s Out-of-Browser feature.  For more information about configuring your application for Out-of-Browser click here.  In this post we will look at how to configure and record your test in WebUI Test Studio and then execute.

To get started first open WebUI Test Studio and create a new project and test.

In order to configure a test for Silverlight Out-of-Browser recording, click on the “Out-of-Browser” option in the menu.

After selecting the SLOOB button, you ...

In Part 1 we looked at how we can use WebUI Test Studio’s Execution engine to execute tests either using an individual test or a group of test within a test list.  In Part 2, we are going to look at how we can take the results of our execution and publish them to a non-default location.

Let’s take a look at the first two options for results publishing, out=[folder path] and root=[folder path].

The out=[folder path] option allows us to copy our results file to any directory on our computer.  For example, let’s say that we multiple projects ...

WebUI Test Studio comes with two options for test execution.  The first is the result of our tight integration with Visual Studio and uses MSTest.exe.  The second, and the subject of this post, is the built-in execution engine ArtOfTest.Runner.exe.  In this post we will look at all the command line options for the ArtOfTest.Runner.exe.  In Part 1 we will look at the two execution command line options as well as how to simplify working with the command prompt.  Part 2 will be dedicated to showing the flexibility of the execution engine by showing the results publishing options.

The ArtOfTest.Runner.exe is ...

The Test List is a great way to organize tests and get execution results summarized at the Test List level. WebUI Test Studio includes the standard “Static” Test List that allows you to add existing tests from your project, but there is a small maintenance penalty for using the static list because each time you add a new test to your project it must be added to one of the existing test lists.

One of the underlying principals of WebUI Test Studio is to decrease the overall maintenance cost traditionally associated with automated testing.  Within the world of test lists ...

Automated testing can be broken into two parts from a process perspective.  First, there is the creation of the test in which you record all of your actions and verifications for a particular scenario.  Second, you execute your test on a frequent basis in order to find regressions in your application.  In this blog I will demonstrate a simple option for scheduling your tests for execution using a built in feature of Windows.

For WebUI Test Studio users that do not want to use Team Foundation Server to schedule test list executions there is a great alternative already built into ...