A few days ago Brian Harry has announced the New Features and Testing Capabilities that will be released in what the call “Feature Pack 2” that is dedicated to the Testing World.
Between these features there is the one thing that many are waiting for: The Recording for Silverlight!
Below you can read more about the grate features that will be released with “Feature Pack 2”, the list is taken from Brian Harry’s post that you can read here.
Has Soon as this pack will be released I will let you know…
Testing Silverlight Applications
Now you can test your Silverlight apps as well as your other desktop applications. We’ve added support both for coded UI tests and for record and playback in Microsoft Test Runner (part of Microsoft Test Professional). You are able to record the execution of your Silverlight app and gather rich bug data (including action logs, video, environment info and more). Unfortunately, you can’t get Intellitrace logs at this time. We’ve tested it on a range of Silverlight apps, including ones with customer controls and apps generated by LightSwitch. We are waiting on a few fixes for LightSwitch issues we discovered – they should be available in the next LightSwitch pre-release.
Perhaps the biggest limitation is that, for now, our Silverlight testing support only works for Silverlight 4.0 applications hosted in IE. In the future, we will add support for desktop Silverlight applications too. There are a few other restrictions that you can read about in the docs that accompany the release but all-in-all, it’s a big step forward for testing Silverlight apps.
Recorded test playback on FireFox
With our Visual Studio testing tools today, you can record and playback web applications in Internet Explorer. With Feature Pack 2, you can play back those recordings on FireFox as well. As with our Silverlight support, it applies to both Coded UI tests created with Visual Studio and automation recordings created with Microsoft Test Professional.
Among other things, this will enable you to create a set of tests once and use them to regression test on both IE and FireFox! Now you can make sure your changes don’t break apps across multiple browsers.
Coded UI Test Editor
Managing your coded UI test has just gotten easier. In VS 2010, a coded UI test is generated as an XML description and some code. Neither is particularly easy to approach if you want to make some minor tweaks to your test – like change how a control you are testing is identified or remove a superfluous UI gesture, etc. The new coded UI test editor in Feature Pack 2 makes tweaking and customizing your recorded tests MUCH easier.
The test editor is accessed by opening the UIMap.uitest item in solution explorer (the coded UI test editor is the designer for it and opens automatically). Below is a picture of the main designer window. On the left is a list of the actions that were recorded. You can edit them and their properties. On the right is a hierarchy of all of the controls that were used. You can edit those too (for example, changing the properties used to identify the controls).