Telerik does not support test studio assemblies in .net standard and does not have a test runner in .net core. Considering all of our Azure DevOps and container agents are running linux we will not be able to use the tool.

Please add this feature to your product.

Test Studio scheduled runs sometimes start browser in the background and it loses focus. Due to that the test steps are not executed correctly and the test fails unexpectedly.

This does not happen when running the test or test list locally.

I am presently working on a government contract and on a virtual machine they can not give me administrator rights because of resent hacks a policy.

Can I please get a contact number and email address that I can have the system administrator talk to and try to get this problem fixed because I am a contractor

and have been working with them to get this fixed and we have not been able to resolve this and because of this no testing is getting done for automation.

Please help I have been using telerik for over 5 years and this is the first time I have had this problem

 

Thank you

Donna DeVries

ddevries.ctr@ntia.gov

bigdjdv@cox.net

402-672-2898

 

Using the Telerik.ApiTesting.Runner.exe to execute API tests cannot output results in junitstep format. It throws an error if using the -f junitstep option when running tests or test suite:

[ERROR] Not supported test results format
Parameter name: junitstep

Hi Team,

 

I hope my email finds you well and safe.

I successfully managed to setup executive server. 

 

This ticket is not an issue but a suggestion from a team member of my company.

 

On the executive dashboard page it would be nice to have a description to show what this test list do. Think that the description it will be something that i will write it somewhere and show it up on the executive dashboard.

 

Thank you for your support

Kyriakos, Prevention at Sea

The tests and test lists are visible in the Test Explorer and can be run the first time you open the Test Studio project in Visual Studio 2019. After any changes or rebuilding the solution, the tests and test lists disappear from the Test Explorer.

The issue is related to the latest version of Visual Studio 2019 and is recognized in build 16.10.2.

DisplayLabels can contain text, but because it is not a supported FrameworkElement, it is difficult to work with in code. Tests instead have to store a path to the element and use the full name - like Applications.MyApp.MyWindow.DisplayLabel1 - every time I want to refer to it. It leads to a lot of repetitious code as well as storing of unnecessary elements, especially where a Find.AllByType would otherwise be able to take advantage of the consistent structure.

The problem we're currently having is being able to leverage Test Studio in the same capacity of distributed testing through Azure DevOps which our IT organization uses for Continuous Integration.

Although the AOR-CLI does provide some benefits, it significantly is missing distributed testing which creates a large bottleneck in the turn-around times of our tests.

A potential way to solve this, as I've seen other testing platforms, is create a Test Studio Add-on for Azure DevOps in which you can handle calling your tests in the same fashion that you can from the Test Studio platform

As our team has grown, we have seen Test Studio record elements that already exists but with different naming conventions and under different pages.

Although I understand that much of the element class (pages.cs) is dynamically produced, I think it would benefit the end user to be able to drag/drop organizing the elements much like you can in other solutions.  This would help the end user have a better organized and less chance for duplication/mess of elements.

Make it possible to choose whether or not to group the results from all iterations and provide average time, when exporting the results. 

I have 20 iterations of the same steps and it will be helpful to see the average time for each step.

Currently the exported result contains extended details only for the failed steps. If there is a warning for a step - like the warning that the element was found only by image, this can be only seen in the Test Studio result file. 

Extending the HTML exported result to show the step warning details will be very useful for anyone who review this type of result (attached in an email after a scheduled run, for example). 

Update the predefined device config settings with the latest available common iOS and Android devices. Check if the User-Agent request header needs to be updated as well, or more options to be provided. 

We have a large PDF (60+ pages) and try to verify certain content on specific pages. During the recording process some elements are captured with TagName and TextContent and others with TagIndex. In this scenario TagIndex is not reliably, because the document is large and the elements change dynamicaly.

One solution is to update the element's find logic manually on all elements that use TagIndex, but this is very time consuming. 

Another option is to use coded step to find the target element by TextContent and verify it.

When the Scheduling server is not added during installation, the Configure button in Test Studio will be greyed out (disabled). It will be helpful to add some kind of tool tip or note about this.

The solution is to modify the existing installation of Test Studio and add the Scheduling Server feature to the installation.

Allow users to add custom arguments when executing tests against any of the supported browsers.

This includes the Chrome Headless execution, which always defaults to en-EN language argument for example and you can't change it.

Hi,

 

We are unable to use TestStudio for WPF, when closing the window during recording we get an excpetion.

I tried and created simple wpf app in VS 2019 and get same results.

I attached a C# project as solution was to big.

 

 

Simple app is based on VS 2019 telerik for WPF project, created as blank.

Only code changed is adding a DispatcherUnhandledException on App class.

Handler:

private void OnDispatcherUnhandledException(object sender, DispatcherUnhandledExceptionEventArgs e)
        {
            if (e.Handled || e.Exception == null)
            {
                return;
            }
 
            e.Handled = true;
 
            MessageBox.Show(e.Exception.Message);
        }

 

Steps:

1) Create new project

2) Create new test for WPF 

3) Configure to the WPF app exe file

4) Click record

5) After test studio is connected close the window.

 

Expected results:

Window get closed without any problems.

 

Actual results:

While closing the window exception is being thrown that we.

 

When generating videos for the test runs from a test list, the output video files uses the name of the test only. There is no indication which is the test list from which this test was executed and when having multiple runs and videos it is difficult to relate these with the generated results. 

It will be useful to generate the names of the videos from a test list in a way to correspond to the test list name and particular run. 

Add the option to start quick execution of tests in Headless mode from Visual Studio.

Currently it is available from the Select Execution Browser window, but if you have selected a preferred browser this window is skipped.

Navigate to the application under test and click a link that opens in a new tab. Then, click within the new tab to redirect it to a new URL and close the tab. 

The result is that the Close pop-up window step is successful, but the tab is not closed. This results in issues with the following steps in the test scenario.

Nested data driven tests generates quite large results, even when there is no data in the bound data table (built-in or external). The result is almost twice the size of the same tests, if these are not using the data tables. The tests may be using InheritParentDataSource, but the behavior is similar if these are not using it as well. 

For real user scenarios, the large results may exceed the limitation of the file size (16MB), which can be transferred through the storage service. 

Investigate if it is possible to optimize the data driven test results, at least for the case, when the data source is empty.