Productivity

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

Note: A Knowledge Base article exists with a link to the sample code used in this post. Note: A previous blog post was written with some basic information regarding TeamPulse integration. The 2011 R3 release of TeamPulse has brought several significant changes to the product, and chief among them from an integration standpoint are the inclusion of forms-based authentication and role-based permissions. These changes extend beyond the TeamPulse client interface right through the services below, which means that any requests to read or write data must be accompanied by a proper authentication cookie representing a user that has the required ...

In my previous post, i showed how JustMock picks mock expectations based on current context without the instance being injected. Based on feedback we found that It’s sometimes confusing and often does not work as intended. However, the context of this post is not to introduce future mocking rather a new feature that allows you to skip mock instance intentionally (when you can’t pass the dependency through a constructor or via method argument) instead the tool is applying it for you on behalf. You can find more on future mocking and some abstract behind it from my previous post: http://weblogs.asp.net/mehfuzh/archive/2011/09/30/future-mocking-revisited.aspx Now moving forward, i...

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