Download dialog which is triggered from a new tab fails to be handled when running a test in Edge and Chrome extensionless mode. 

Such download dialog is usually triggered with a link similar to this: 

<a href="100MB.zip" target="_blank">Link to donwload</a>

The download dialog looks like this: 

When trying to connect Test Studio project to Git source control the following error message appear:

The below snippet to find specific element fails to return the expected element. The Content is of the same element regardless of the "parent()" method.

 var item = Find.jQuery()
                    .tag("div")
                    .classes(new string[]{"className"})
                    .contains(name)
                    .parent()
                    .first()
                    .Content;

Specific customer application requires double click to trigger an action. When running the test without extension, the double click is not executed as expected and the test fails on the next verification step. 

Workaround Enabling the usage of extension for the browser (Chrome and Edge) resolved the misbehavior. 

Additional details are shared internally!

I tried to add Excel data source to my project and bind it to existing web test, but encountered an error during execution. The execution log states that there is no actual data, which is not true.

After discussing this with the support engineer, it seems that the issue is related to the Access DB driver. Test Studio works with the 32-bit version and the new Visual Studio 2022 works with the 64-bit version.

As a workaround I can use an older version of Visual Studio.

Image verification step fails whith following exception when executed on specific machine. 

Executing a test with double click action on Windows 10 machine with Chrome browser, enabled for automation with extension, is failing on the double click action when executed in code. 

Test Studio version 2022.3.xx. 

Sample test shared internally.

I am not able to add Test Explorer Settings to my project in Visual Studio. I am missing the assembly LoadTestPackage and I was notified that this feature has been deprecated in VS 2022.

The support team at Test Studio mentioned an alternative solution with the Run Settings as possible solution, but it is not yet implemented.

By design the Wait for exist step doesn't record an image for the element. However, you can manually add an image for the element in that step. And if this is the case the fallback to image search (when the find expression doesn't match an element on the page) remains only in the background - there is no message that the element is found by image only in the execution log. 

Steps to reproduce:

1. Use a wait for exist step with an image for the element.
2. Ensure the element find logic will fail to locate the element.
3. Ensure the image will match an image on the page. 
4. Run the test. 

Expected: The element to be located by image as a fallback search criteria and get the message and warning in the execution log for that. 

Actual: The test passes, but never informs that the element was found by image only.

1. Local scheduling setup - default installation of Test Studio with no services added.
2. Project is connected locally.
3. Schedule a test list (recurring or for some time ahead).
4. Make a change in a test from the test list. 
5. Save the changes - the automatic upload prompt appears on each save action. 
6. If you choose to not show it again, the automatic upload gets triggered without showing that notification.
7. As a result it produces error message saying "Scheduling service at http://localhost:8009 is reporting that it cannot communicate with Storage Service at http://<theMachineName>:8492/v1". 

Expected is that there shouldn't be any calls to the Storage Service.
Actual is that the attempt for upload to the Storage is triggered for local setup as well. 

In user's specific application there are kendo menus implemented with sub-menus to appear on mouse hover. During recording all menus can be opened as expected only if highlighting is not enabled. Once highlighting is on, the submenus are shown over the main menu and no clear selection can be made. 

Further details on the case shared internally!

Workaround: The issue could be workaround with the following steps: 

1. Keep highlighting disabled and open the menus as expected. 
2. Use click steps over the menu options to add these as elements into the Test Studio project (in the Elements Explorer). 
3. Use these elements to add the required steps from the Step Builder. 

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.

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. 

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.

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);