Microsoft's long awaited release of Silverlight 5 happened on Friday. Silverlight 5.0 ships with a ton of new features, including new media and graphic improvements as well as extending the trust model to the browser (a big deal for some Line of Business applications). This release happened without any fanfare but that hardly diminishes its value. Some of the great things in the release are listed here. While Microsoft did not announce that there was going to be a Silverlight 6, they did announce they would extend support for Silverlight 5 for ten years until 10 Dec 2021, as long...

Microsoft announced the release of Silverlight 5 a couple of days ago. Telerik is the leader in supporting the new technologies so is our automated testing solution – Test Studio. The Silverlight Test Automation is straight forward with Test Studio no matter the SL version the application is built on top of or the Silverlight runtime on the client machine. The latest official Telerik Test Studio version released a couple of weeks ago and labeled 2011.2.1117 officially supports Silverlight 5. Download the bits from here! We also recommend the latest internal build, labeled 2011.2.1209 (yes, released the same ...

NOTE: I’m running a series called “31 Days of Testing” on my personal blog at FrazzledDad.com. The series covers a really broad range of testing topics, so I haven’t been cross-posting things here. This specific post; however, hits perfectly on things I’ve spoken about in Test Studio webinars and previous posts, so I’m posting it here, too. I’ll cross-post a few others; however, if you want to read the full series then please join me over at FrazzledDad! I wanted to write a blog post on “Introduction to Functional Automation Testing” but I realized I firmly believe there are ...

Introduction The Silverlight 5 Release to Manufactures (RTM) is now available to download from the Silverlight site. Telerik is very excited about this release as well as WPF as you can see in our latest Q3 webinar. We can confirm that all of our tests against the latest release were successful. We will be releasing the SL5 build shortly but no longer than the end of the month. Please use this release to update your Silverlight 5 Beta/RC code to work with and use the new features. Download the bits: Visual Studio 2010 SP1 or Visual Web Developer Express 2010 SP1 is...

When asserting an expected call for its number of occurrences or may be just to verify if the setup/arrange is acted as intended, the tool generally raises assertion that points us to the reason why the test failed. Different mocking tools use different exception classes therefore there is no common way to consolidate them. However, if we just take a look into the test framework unless its some alien one, they all have a common underlying structure for Assert.Throws or ExpectedException (MSTest). MS Test (C# and Silverlight) Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException NUnit NUnit.Framework.AssertionException XUnit Xunit.Sdk.AssertException MSpec Machine.Specifications.SpecificationException MbUnit Gallio.Framework.Assertions.AssertionException So the point here is that if we just use the existing exception class rather...