Uploading multiple files works in Chrome with the browser in extension mode. This functionality is missing in extensionless mode and the test execution fails. Please provide a solution for extensionless mode.

As a workaround, there a coded solution here.

Depending on the implementation of Kendo Menu via ASP.NET Core it returns different HTML. In the case where we use Html.Kendo it is generated in a way that works well with all built-in methods in the translators.

However, if we use tag helper syntax instead, the structure of the Kendo menu element is different and the code below times out.

KendoMenu menu = Pages.Home.MenuNavigation;

KendoMenuItem menuItemSettings = menu.AllMenus.SingleOrDefault(x => x.MenuItemTitle == "title");
menuItemSettings.MouseHover();
Wait.For(x => menuItemSettings.AllOptions.Count > 0, menuItemSettings, 5000); // running into a timeout, because menuItemSettings.AllOptions always 0

It would be helpful to extend the functionality of the Kendo translators to include both types of DOM structure. We are using Kendo UI version 2022.2.510 and Test Studio 2022.2.804.

Kendo Angular Daterange component is not supported via built-in translator in Test Studio. But it can be automated out-of-the-box by typing the data directly into the input field with slight adjustment of the step: 

1. Ensure the element find expression doesn't use the dynamic id of the input.
2. Increase the step property TypingDelay from 50 to 100 to slow down the typing a bit.
3.  Sample test is attached.

When executing this test with the recorded 'Enter text' step in Chrome and Edge it works fine. 

When executed in Firefox, the date isn't populated correctly as it gets typed only in the year section of the date input. 

Expected: The recorded step should behave the same for all browsers. Can this be fixed?

Workaround:  The current solution is to convert the 'Enter text' step into code and specify the coordinates of the click action so that the click happens on the left from the input center. Modified coded step is available in the sample test. 

Steps to reproduce: 

1. Start a recording session with a browser (Chrome or Edge) without using the Test Studio extension. 
2. Navigate to a page where you can download a file and trigger the download.
3. Insert the file name and choose a folder to save the file. 

Expected: A 'Handle Download Dialog' step is added to the test and the file is downloaded.
Actual: A 'Handle Download Dialog' step is added to the test but the file is not really downloaded and you can't find it the specified folder. 

The 'Handle Download Dialog' step is recorded correctly, though, and you can use it for execution. During test run-time the file gets downloaded correctly in the specified folder. 

The application under test [Matrix] crashes, if the Test Studio recorder is attached and we execute a specific click step that opens a Save Dialog. The process to reproduce it is with Run -> To Here on the previous step and then Run -> Selected Steps on the problematic step.

The application under test freezes and ultimately crashes. There is no issue if we execute the whole test, or execute it with Run -> To Here after the problematic step.

Visual Studio 2019 crashes after opening and closing tests and working on them for some time. The memory that Visual Studio uses increases to the point where it slows down and eventually crashes. 

There are errors from VSTSExecution in the Windows Event Viewer log and other errors about faulting module "C:\WINDOWS\System32\KERNELBASE.dll" from the time of the crash.

Which Windows Server versions are supported for use with Docker containers? The documentation here only shows how to setup up a Docker container on a Windows machine, but not on Windows Server and other images.

Please specify which version and images are supported for testing with Run-Time in a Docker container.

When generating chained find expressions Test Studio always uses the id tribute for the parent element and it doesn't take into account the actual order of attributes.

Then, if you completely remove the id from the find logic list settings, the generated find expression uses only TagIndex for the target element and no chained find expression. 

Generating this type of expressions need to be revised. 

Example shared internally!

MaskedInput date field behaves inconsistently when automating the control. The type text action often types all numbers in the currently active part of the date (the year for example).

The workaround is to identify the exact sequence of actions, which allows entering the text correctly - for example, click on the input, press the Home key, press the Delete key to remove the current date, enter the desired date. 

It will be great to improve the steps recorded out-of-the-box for that type of control.

Specifics shared internally. 

Trying to set a variable in API test from a Json response body, but the used Json path isn't matching anything from the Json file. If testing the same in https://jsonpath.com, it returns the expected value. 

Specific details shared internally!

We have a dynamic test list that includes several tests based on specific criteria. We executed this test list remotely once, but later decided to delete a few of the tests from the project. 

The dynamic test list shows the correct set of tests that should be executed, but when we execute it remotely, we noticed that the previously deleted tests were still executing.

There is no way to sync the current project with the storage server and the only workaround was to drop the project, tests and test lists from the MongoDB.

We use Test Studio with Visual Studio and we are able to use the Pending Changes feature of Visual Studio to see that we have changed certain test scripts and to check them in to source control. 

It would be better to show changes of tests and steps in a more human readable form. This applies for Test Studio projects that are under source control in Test Studio IDE or in Visual Studio.

Verification for OuterMarkup is failing after the original recorded steps is converted to coded step. The workaround is to add a Wait for Exists step against the target element either as a recorded step or in the coded step. 

Sample code for wait step:

Pages.TelerikTestWindow.AtvcapDiv.Wait.ForExists(30000);

Some actions in specific application with frames cannot be recorded as expected.

The last version of Test Studio when this was working fine is R3SP1 2020 (v.2020.3.1209). 

Further details shared internally.