Telerik blogs
Accelerate Your Test Automation with Test Studio—Webinar Recap_870x220

Have questions about Telerik Test Studio and how you can use it to accelerate your test automation? We answer them in this recap of our Test Studio Webinar.

Telerik Test Studio is an ultimate test automation solution for web, mobile and desktop applications that can be used by both developers and QAs. It can be applied for Functional, Performance, Load and API testing needs and integrated with today's latest technologies including Angular, React, WPF, MVC, AJAX, RESTful, etc. 

Relive the Content

On August 2nd 2018, we hosted a webinar that answered the following questions:

  • How to quickly get up to speed with test automation
  • Why Test Studio is the best tool for Kendo UI application test automation
  • How to easily integrate API calls in your web functional tests to decrease the risk of script/environment failure and to speed up automation.

Your hosts were Andrew Wieland (Manager Sales Engineering working with Test Studio for more than 5 years) and Iliyan Panchev (Product Manager for Telerik Testing solutions with extensive experience in QA). 

It was an awesome hour. We started with Telerik Test Studio basics, but quickly moved into deep dive discussions and showed off some practical demos. If you could not make it for the live webinar, you can relive the webinar in its entirety—high definition recording available now!

Additional Questions and Answers

One of the most enjoyable aspects of our webinars is the audience interaction and Q/A all throughout. We appreciate developers and QAs bringing up real-world questions and concerns on their latest needs and pain points.

While we tried to answer as many questions as we could on air, here’s an excerpt of some short Q/A topics that were important to resurface:

Q: What are the basic prerequisites for test automation?

A: See our System Requirements Page for recommended and minimum technical requirements to be able to use Test Studio. Beyond this, it depends on what type of application you are trying to test and the will of the tester to start automating. Test Studio takes a lot of the engineering out of automation, but it is also very important to choose the right tool for technology that you are going to test and the expertise of the team. Our recommendation would be to kick off a 30-day trial and try Test Studio out. This tool is known for having a very low learning curve, but we also give you access to our engineering-level support and pre-sales consultation.


Q: When we build our tests should we use the record button in the top left or should we be building them manually?

A: Most teams will start by recording their tests by either clicking on the record button, or right-clicking on the test name and selecting recording. Test Studio will capture most actions (clicks, drag and drop, dialog handling, text input, etc.), while the highlight element feature will enable you to add many more custom steps/verifications/etc. Once recorded, you can easily modify your tests, record new steps in the middle of an existing test, and add more customization from the toolbars, all without code OR you can do all that plus editing steps in code, add anything in C# or VisualBasic code if needed, even adding a third party libraries.


Q: Does Test Studio work the same with a WPF Desktop application?

A: Yes, the difference is just in pointing the WPF test to the application .exe instead of a browser and url. Check this out for more information.


Q: Is it possible to use a Test Studio test as a part of Visual Studio Online Build and Release process?

A: Yes, you can find more detailed information on this topic here. Our command line runner allows you to plug Test Studio right into any build/CI process, so your tests will kick off automatically once a build is compiled and a batch command is sent to the test runner.


Q: How do you create API tests?

A: The API tests can be recorded, created manually, or imported from Fiddler. If you want to learn more about API testing you can check out this blog post.


Q: How is the CSRF token handled?

A: As soon as you can retrieve the CSRF token from the server e.g. as a part of html or cookie, you can extract it as a variable and include it in any of the following http request with a variable reference.


Q: Can Telerik Test Studio work for Telerik Xamarin Forms?

A: In general, yes, but it depends on the implementation. We have a free 30-day full featured trial, so you can try Test Studio for Mobile and see how it works with your application.


Q: Can Test Studio be integrated with Atlassian Jira or any other incident management tool?

A: Yes, Test Studio integrates with Jira and TFS out-of-the-box, but also features extensibility APIs that allow you to customize integrations with most file-based systems.


Q: Does Test Studio support Nativescript?

A: Yes, it supports testing on NativeScript mobile applications, and even offers built-in configuration for making your app ready to test.


Q: Can we get the trial version of this tool ?

A: Yes, you can download a free 30-day full featured trial with a single click. Please feel free to contact our sales team for customized assistance, technical consultation, and even a live demo (


Q: Is there Git integration with Test Studio or any way to save tests in source control?

A: Yes, Git is supported out of the box, along with TFS/VSTS. Check this out for more information. Similar to bug tracking, the Telerik Testing Framework can be customized to integrate with most file-based systems, including SVN, etc.


Q: Is there any way to pause a test list that is currently executing?

A: For Test Lists, you can abort a test from within Test Studio, but if you are running the test in quick execution mode, usually when crafting a test, you can pause a test at a current step from the visual debugger that runs with the test.


Q: I often have to create Web Test automation for third party Webs. That's Web pages that I don't own the code, neither I know the Technology. Can I use Test Studio?

A: Certainly! You don’t need to have access to the program’s source code for web-based applications. If it produces a DOM-based website, it can be automated with Test Studio. Knowing the type of technology that the app was built with can always help, but we provide lots of tips and samples for configuring the element find logic to work with different technology types (Angular, JQuery, Ajax, etc.).


Q: To use the API test as step would we need the API testing module for Test Studio?

A: Yes, since this is how you will be able to create an API test to be referenced as a step in your web test. All of which are included as part of Test Studio Ultimate.


Q: As my old knowledge, to start using API testing, we testers must depend on the product supporting API calls, e.g. via HTTP post. Can Test Studio API testing avoid this product support?

A: Yes, it can, Test Studio for APIs supports API calls, you can examine requests and build API tests without the need of other product.

Q: How did you add Data Driven find logic to an element?

A: While editing the element logic (either through the edit-in-live mode or from the step failure details), you can click on the drop-down arrow next to any variable field and a drop-down menu should appear with the names of all columns from a data source that is already bound to that test. See Data-driven find logic.


Q: The company I work for does not have "testers". Each developer is expected to write all necessary tests for the code they develop. The price per seat for Test Studio is reasonable for someone who uses it every day. It is too high for devs who might use it 3 or 4 times per year. Could you offer it under some flexible licensing structure where 3 licensed copies could be available for a pool of 15 developers? (Only 3 copies in use at any time.)

A: Test Studio’s full licenses are floating, allowing you to deactivate/reactivate the license machine key from machine-to-machine, without having to uninstall anything. You can easily store your test projects in source control and pick up the latest version of any project, no matter where the license may be active. Thus, you only need to purchase the number of licenses based off how many simultaneous users will need them. We also have Runtime licenses for machines that only need to execute tests, schedule test lists, integrate into your CI/Build process, monitor performance, distribute load, etc. at a much cheaper price-point.



That’s a Wrap

Thanks to Telerik Test Studio, this may be one of the best times to accelerate your test automation. If you are not still our customer and want to learn more about Test Studio, you can download a free trial and dive deeper into the solution. If you are our customer stay tuned about the forthcoming features in the October release this year. If you have a special issue or need a targeted demo for your specific case, you can contact us.

Adios and happy testing!

About the Author

Galina Jordanowa

Galia is a Senior Product Marketing Manager for Telerik UI for Blazor, Telerik UI for .NET MAUI, Telerik Reporting, Telerik Report Server and Telerik DevCraft at Progress. She has 23+ years in marketing, improving the sales, performance and reputation of a great number of international companies. Outside of work, she enjoys reading, psychology, mountain climbing and music. Follow her on LinkedIn.

Related Posts


Comments are disabled in preview mode.