Productivity: Testing

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 ...

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...

Did you miss yesterday’s Q3 Webinar on Functional and Performance Testing with Telerik Test Studio? No worries—you can now find it on Telerik TV! I run through the features we’ve added to Test Studio in our Service Pack 1 release for Test Studio 2011 R2. Some of the things you’ll see in this video: Using the new Test Owner property to help identify who to talk with when a test fails Gathering profiling data from multiple servers Walking through the new, improved Compare view to see differences between two performance run passes Using our new feature that prompts you ...

In my last post I talked about some ways to organize your tests to help keep things clear and discoverable. My pal Adam Goucher, one of the top Selenium folks around, took me to task me via mail (in a friendly way!) that tags and metadata are a critical part of organizing your tests. I agree, but with a subtle difference. Tags and other forms of metadata are great for helping you categorize your tests, but I think they come in to play more when you’re trying to execute your tests versus organize your tests on the file system. ...