Productivity

I’ve just posted up a new video on Telerik TV, Common Functional Testing Problems, which will help you understand three common issues people run in to when working with automation for web applications: JavaScript interfering with text injection into input fields Dynamic data (such as AJAX or Silverlight service calls) where Elements you need to interact with aren’t present on the page until after a service call completes The elements you need to interact with are on the page, but the content in them isn’t present until after the service call completes The video walks you through each of ...

Although it was only a month ago when JustTrace Q3 2011 was released, we've launched JustTrace Q3 2011 SP1 with two new major features: a completely redone “Live Data” view and the ability to view source code. In addition, a number of enhancements have been made, resulting in a smoother user experience. Visit the What’s New page for a list of all changes. Live Data View The Live Data view has been updated to provide visual information via charts representing CPU and memory usage. This enables you to visualize how the profiled application process is currently affecting performance and memory consumption. More importantly, you now see...

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