Productivity: Testing

One of the key factors to the increased popularity of jQuery is its powerful selector syntax that can be used to find elements in the DOM. The syntax enables simple selections like selecting an element using an ID (#my_id) to more complex mutli-element selections and filtering. The power and popularity of jQuery selectors prompted many of our customers to request support for similar selection/query syntax in our WebAii Testing Framework. It is worth noting here that WebUI Test Studio is built on top off the WebAii Framework and customers using WebUI Test Studio have full access to the framework API ...

As JustMock is approaching its release date I decided to blog about it and more precisely about its dual nature. Probably you already know JustMock supports two (proxy and elevated) modes. That's why I am speaking about duality. In fact the duality in JustMock has many aspects. We could even say JustMock was built on two continents as one of the brains behind JustMock is working remotely on the project. So, duality is everywhere :) By the way, check out Mehfuz's blog, it is excellent place where you can see JustMock in action. I've been thinking for some time about doing...

Automated testing can be broken into two parts from a process perspective.  First, there is the creation of the test in which you record all of your actions and verifications for a particular scenario.  Second, you execute your test on a frequent basis in order to find regressions in your application.  In this blog I will demonstrate a simple option for scheduling your tests for execution using a built in feature of Windows. For WebUI Test Studio users that do not want to use Team Foundation Server to schedule test list executions there is a great alternative already built into ...

The default behavior of the WebAii Testing Framework (and WebUI Test Studio respectively) searching for the application visual elements is to timeout after a certain period of time if the element is not found. [TestMethod()] public void TelerikComSLTest1() { // Enable Silverlight testing Manager.Settings.EnableSilverlight = true; // Launch an instance of the browser Manager.LaunchNewBrowser(); // Navigate to : 'http://www.telerik.com/' ActiveBrowser.NavigateTo("http://www.telerik.com/"); SilverlightApp app = this.ActiveBrowser.SilverlightApps()[0]; Image titleImage = app.Find.ByName<Image>("Title"); // will timeout if the image name is changed // Wait for visible 'TitleImage' titleImage.Wait.ForVisible(); // do whatever else is needed ...

Writing state of art unit tests that can validate your every part of the framework is challenging and interesting at the same time; it's like becoming a samurai. One of the key concept in this is to keep our test synced all the time as underlying code changes and thus breaking them to the furthest unit as possible.