Book Image

Learning Software Testing with Test Studio

By : Rawane Madi
Book Image

Learning Software Testing with Test Studio

By: Rawane Madi

Overview of this book

Test Studio is Telerik's QA solution for automating your manual testing. With Test Studio's standalone edition or Visual Studio plugin, you can rule out the possibility of unreliable test execution and UI recognition, non indicative test results and reports, dispersed test repository, low code coverage, and unaffordable learning curves. With no code, this tool provides an intuitive IDE to effortlessly create maintainable tests. If you are looking for a solution to automate testing for your web, desktop, or mobile application, you can now benefit from Test Studio's rich automation features. "Learning Software Testing with Test Studio" will illustrate how to reliably automate test cases when it is time to relinquish manual testing habits. This book is all about less theory and more hands-on examples to present a complete manual and automated solution for your ASP .NET, WPF, Silverlight or iOS apps. This book gets you started directly with automation in Test Studio by exploiting its recording powers through series of concrete test cases built around the equipped applications. Each chapter starts with a typical automation problem which is then approached using Test Studio specialized automation features. You will learn how to create record and playback functional, performance, and load tests. Furthermore, we will see how to insert verification steps, logical constructs, convenient logging operations, and how to convert test scripts in order to implement keyword and data-driven architectures. To endow your tests with additional flexibility, each recorded automation feature will be approached from its coded perspective through the usage of the underlying ArtOfTest Test Studio automation library. This book also illustrates how Test Studio can automate pre-conditions, test result inputting, and the capturing of system states during manual test case execution in order to keep the tester's attention focused on the important details.
Table of Contents (18 chapters)
Learning Software Testing with Test Studio
About the Author
About the Reviewers

The element repository

Recorded test steps are composed from two parts: elements and actions. The UI elements constitute the skeleton whereas the UI actions constitute the engine. So the actions are driven against the elements.

As we have seen in the previous chapters, a typical test step looks like: LeftClick on HistoryTextblock. The element is HistoryTextblock whereas the UI action is LeftClick. In the application under test, the way a UI element is identified by Test Studio is through its find expression found in a property called FindLogic. This is a property present on the element and it holds the keys for Test Studio to uniquely find its way through the application object hierarchy to identify that element. At runtime, Test Studio evaluates the FindLogic expression and executes the UI actions on the yielded element. This expression could enclose evaluation conditions either around element properties such as Name or element path in the object hierarchy, for example, XamlPath. This...