FindExpressions are the basis for all element searches in the DOM Explorer. Test Studio features intuitive UI to help users build FindExpressions by modifying a rich and extensible search definition model. Testers are prompted to choose an attribute type which may vary depending on whether it’s a HTML or XAML element you are trying to build FindExpression for. The FindExpression builder also gives users an overview of the element, which and how many tests this element has been used in, as well as quick view of the element in the DOM Explorer.
The Elements Explorer stores the element locators for your entire test project. Thanks to its built-in searching, sorting and filtering capabilities you won’t need to scroll and search through long lists of items. Instead, quickly find an element using the real time search feature or load the elements of a certain test case.
When a test fails, Test Studio enables you to go back and compare the page from the time of recording to the current failing page. Both states are displayed in a split DOM view that shows the Recorded DOM vs. Executed DOM. This enables you to quickly discover the change that caused your failure and fix it.
Most automated testing tools will force you to determine the absolute attributes of an element on a page in order to record any verification against it. This task gets even harder when it comes to dynamic pages. Test Studio brings in a unique find expression algorithm that automatically defines the best attributes to use to locate a specific element on a page.
You can data-drive element identification. By data-driving your identification logic, we have simplified the process of looping over large numbers of elements at run-time. Instead of creating a verification for each element, now you can focus on creating robust verifications that can be applied to an array of elements on your page—all from a single step!
All application elements are stored at the project level, abstracted out and filed in the "Elements Explorer". If there are multiple tests that use the same element, the latter is referenced from the “Elements Explorer” instead of being duplicated in the test. Thus, you can maintain unique elements only, and update them if needed, instead of modifying numerous duplicate elements in every single test.
Copyright © 2002-2014 Telerik. All rights reserved.
Powered by Telerik Sitefinity CMS