Productivity: Testing

Every test suite of any significance will require you to have some form of coded steps. As awesome as Test Studio is, there are always going to be things you’ll have to do via code. Test oracles to check your database or file system would be one example. Backing APIs for setup and teardown actions would be another. Sometimes it’s just handy to have a breakpoint where you can pull up Visual Studio’s Immediate window and do live queries of the web page’s Document Object Model (web apps) or Visual Tree/XAML Tree (Silverlight or WPF applications). I’ve just uploaded a ...

Visual Event is a little tool I found. When I say that I "found" it - I literal discovered it after Google-ing "detect javascript events" or something to that effect. Neither Telerik nor I personally have any affiliation with the Visual Event product or its makers. Anyway the tool will help you determine what javascript events are associated with a particular control. Javascript events are a crucial part of UI automation. Good understanding of how and when they are employed in your app can save you a lot of trouble. 90% of the time switching your step to ...

This post is going to be a bit advanced. If you're having trouble with understanding any of the below information - you can ask in the comments section or post in our technical forum. Or if you're a paying/trial user you can submit a support ticket requesting additional assistance. Ok, so as you may or may not be aware we allow you to extend Test Studio's functionality through plugins. This article gives you a nice breakdown of how you can do that. And as you can see in that article the functionality you're allowed to extend is mostly related to ...

We’ve just posted up a white paper I wrote on getting started with UI test automation. The whitepaper has nothing to do with Test Studio (examples are even in WebDriver via C# !). Instead it focuses on the fundamental things you’ll need to work on in order to have a successful future with UI automation. In the paper I cover a broad range of topics including: UI Automation is a difficult domain. Seems obvious, but you have to acknowledge it up front! Locators, locators, locators. Learn how they work, then learn how the work in your environment. Working ...

Auto mocking containers are designed to reduce the friction of keeping unit test beds in sync with the code being tested as systems are updated and evolve over time. Background The Dependency Inversion Principle states: High level modules should not depend upon low level modules. Both should depend upon abstractions. Abstractions should not depend upon details. Details should depend upon abstractions. As more developers follow this and the rest of Robert Martin’s SOLID principles, methods and classes become much smaller with dependent objects injected into them, typically through constructor injection. As additional dependencies are needed (or the code is refactored to improve dependency isolation), the signatures of...