Test Studio comes with dedicated support for the Telerik and Kendo UI components out-of-the-box. The built-in control types provide methods for invoking actions which are specific to the respective UI component and could otherwise be hard to trigger. Additionally, all Telerik and Kendo UI components have properties exposing the current state and providing easy access to their specific internal structure.
You can read further about the built-in translators in this article.
- What Are the Built-in Test Studio Translators?
- When Do I Need to Use the Translators?
- How Can I Use the Built-in Translators?
- Which Telerik and Kendo UI Components are Supported?
- What Is the Translators Versioning and Which Option Should I Choose?
The Test Studio translators are extensions that open a component and expose its properties. This enables the Test Studio recorder to identify each element and provides you with out-of-the-box action and verification steps for that element that you can add on-the-go, as you record your test in the browser.
Test Studio and its built-in translators facilitate the automation of any application that is built with Telerik and Kendo UI. If the application you need to automate uses Telerik or Kendo UI components take advantage of the translators while you record and execute automated tests that are created with Test Studio.
In practice, when you need to record a test for an application that is built with any Telerik or Kendo UI components, you don’t need to do anything different from what you are used to for automating your projects. While you interact with the controls in your application’s UI, Test Studio recognizes the component under test and lets you add ready-to-use action and verification steps instead of generic ones. If you then check these in the test, you can see custom type of steps specific for that component.
KendoAngularTab : 'New York City' click action.
TelerikBlazorGridDataCell : Click on Cell [5, 4]
KendoGrid: Grid is currently grouped by 'category.categoryname':
Find a detailed how-to guide about recording test scenario for application built with Telerik and Kendo UI.
Test Studio comes with basic translators for HTML, Silverlight and WPF, and exclusively built translators for Telerik AJAX and Silverlight components, Telerik UI for Blazor, Kendo UI for Angular and Kendo UI for jQuery. These translators have a ”base” or ”generic” group of intrinsic translators that are used whenever a more specific translator is not available.
A list of all supported components can be found in the Project Settings -> Translators dialog. The translators for all components are enabled by default. You can choose to disable a specific translator, or a group of translators, but this is not a recommended practice if not advised otherwise by the Test Studio Support Team.
Test Studio is built with extensibility in mind, so as additional components become available, new translators can be introduced and plugged in. Test Studio is committed to maintaining translators in step with new developments in the Telerik and Kendo UI component libraries, which is why you can expect all translators to always be up-to-date.
Test Studio supports the latest available version of the Telerik and Kendo UI components following releases through the years and offers backwards compatibility for previous versions. This means that you can continue using Test Studio even when an application is no longer in active development mode.
The 2022 releases of the Telerik and Kendo UI components introduced significant changes in their structure and appearance. This brought the need of versioning for the Test Studio built-in translators. The available versions and complete detailed mapping regarding which Test Studio release corresponds to what components version can be found in this article.