Productivity: Testing

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

Test Studio Workshop is our new training initiative - a weekly (you guessed it) workshop. Each session will deal with a specific automation challenge. From seemingly basic to advanced use cases that might require some coding skills. We try to tackle common errors seen with new Test Studio users and shed light on little known but powerful features the product offers. The agenda is as follows: The presenter goes through the main information related to that week's subject in roughly 15 mins. From there we go into Q&A mode. The session is set as 30 mins long but we will ...

With each release of Test Studio, we carefully test our integration points with all external systems to make sure we work seamlessly with the latest and greatest versions of these systems. Test Studio has many dependencies that we rely on to offer our customers a great user experience. These dependencies include all the browsers we automate (IE, FF, Chrome & Safari), Visual Studio that we plug-in and recently Quality Center and TeamPulse which we integrate with. With each of these components, we not only try to support the latest and greatest versions but also be backward compatibility with as many ...