Getting Started: Automation Testing with Test Studio Dev

One article with step-by-step quick start guide – what are the first and most important steps in order to have your first viable test from functional point of view (no installation and licensing). The steps will give summarized information about each step. For detailed information there will be links for the respective article from the Features section.

Create a Test Studio Dev Project

Create a new project using the Test Studio Dev template - select Create New Test Project under the Telerik->Test Studio menu.

Create TS Dev project

Next choose the type of programming language between C# or VB.NET and set a meaningful name for your first project.

Name_Language_of_Project

Add a Test in Project

By default the newly created project contains a Web test.

Web Test Included By Default

To add new test in the project click with the right mouse button on the project name in Solution Explorer, select Add and choose between Test Studio Web Test... or Test Studio WPF Test....

Add New Test

The respective item is selected in the list of items, type a name and click Add.

Name New Test

To open the test double click on its name in the Solution Explorer.

Open new test

Record a Test

Note! The supported for recording browsers are Internet Explorer, Chrome and FireFox

Double click a test from the Solution Explorer to open it. Click on the Record button to launch a new browser or an instance of the WPF application to record against.

Click Record Button

Once the browser/application is launched the Test Studio Dev recorder toolbar will be attached to the that instance and will record steps in the test for each action against the application under test.

See also:

Elements Explorer

The Elements Explorer displays all elements included in the test during recording the test. It is similar to the DOM Explorer in that it displays a tree of elements, but the Elements Explorer only contains elements you want to use in your tests. Also, the elements in the tree view have properties that are more specific to testing.

To open the Elements Explorer in project click on the Show Elements Explorer button. It will appear in the lower middle pane next to Error List and Output tabs.

Show Elements Explorer

The Elements Explorer can be also shown on screen from the Telerik menu.

Open Elements explorer from Telerik Menu

Execute a Test

Note! The supported browsers for execution are Internet Explorer, Chrome, FireFox, Microsoft Edge, Safari.

Test Studio Dev tests could be executed from the VS Test Explorer or with the Test Studio Dev Test Runner.

Test Studio Dev Quick Execution

To execute the currently opened test click on the Execute Test button to select a browser to run the test against.

Quick Execute Test

An instance of the selected browser will start and all recorded actions in test will be executed.

Read more details for the settings which could be applied for the test run.

VS Test Explorer Execution

The Test Explorer in Visual Studio automatically lists and provides all Test Studio Dev tests for execution.

VS Test Explorer

Ensure the project is re-built before initiating a run from the VS Test Explorer. Any recent changes will not be reflected otherwise.

Run the tests with the Run All button. Or choose a group of tests to run from the dropdown options of the Run... button in Test Explorer.

VS Test Explorer Run Tests

An instance of the selected browser will start and all recorded actions in test will be executed.

Find further details for the Test Explorer execution.

Executing Tests in CI Environment

Include a short summary and links to the respective articles.

Test Results

Each test run generates test results.

View Results

Test Studio Dev Quick Execution displays the outcome of the executed test in overall and writes verbose results info in an Execution log. The test results are available for review as long as the test stays opened in the solution or until the Clear results button is clicked.

Quick Execute Test Results

The Execution log provides details for the executed steps in the test.

Quick Execute Test Execution Log

VS Test Explorer displays the results of test execution under the list of test in Test Explorer pane. These are in the same format as the results generated by Test Studio Dev execution. The test results are available until the project/solution stays opened.

VS Test Explorer Results

Debugging Failed Test Results

The test execution will be terminated in case a step fails and the test will be marked as Failed.

Test Studio Dev displays status for each step in the test - Passed, Failed, Not Run. Hovering over the red crossed circle in front the failed step will show a tooltip with details about the failure.

Failed Step Tooltip

Double click on the red crossed circle opens the Step Failure Details dialog. It provides detailed description of the failure reason and additional debugging options.

Failed Step Details

VS Test Explorer displays the test as well as Failed. The test result is under the listed tests and displays the common information for the failure as it is listed in the Execution log.

VS Test Explorer Failed Results

Coded Steps

Test Studio Dev Edition allows you to implement coded solutions for scenarios that require more complexity than what can be composed with recording your actions or building advanced steps with the Step Builder. You can create new or convert existing steps to coded ones, define your custom logic in code behind files or any custom library that your projects links to. For more detailed information read the following article.

Is this article helpful? Yes / No
Thank you for your feedback!

Give article feedback

Tell us how we can improve this article

close
Dummy