The project is initially created in the standalone Test Studio IDE and is connected to a remote Git repository. Then it is exported to Visual Studio and when trying to run test lists in the VS Test Explorer, they don't start at all. 

The Tests output contains an error when trying to run a test list: 

Error preparing project for command line run: Could not create an instance of type ArtOfTest.Common.SourceControl.IRepositoryInfo. 

The workaround is to clear the Source Control Binding from the Test Studio Standalone IDE with the options Discconect from Source Control and then Remove Source Control Binding. See these options in the screenshot from this link.

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.

Visual Studio 17.4.3 crashes when your rebuild a Test Studio project.

To reproduce the issue you need to create new project with only one test and a few steps. Then, build the project and Visual Studio becomes not responding.

Currently sending a dynamic target towards JSON POST data replaces the complete string. 

Add the ability to parse the JSON POST data and replace only certain parts of it. 

Steps to reproduce: 

1. In a test add an element through the highlighting menu -> Add Element to Repository.
2. Create a step through the Step Builder for that element.
3. Convert the step to code. Note: The test should not use any other recorded element in code. 
4. At this point the element is only referenced in the test as Independent.
5. Locally it is executed with no errors. 

Expected: To be executed with no errors on a remote machine. 
Actual: When executed through the Scheduling it results in compilation errors similar to this: 

 error CS1061: 'ProjectNamespace.Pages' does not contain a definition for 'PageNodeFriendlyName' and no extension method 'PageNodeFriendlyName' accepting a first argument of type 'ProjectNamespace.Pages' could be found (are you missing a using directive or an assembly reference?)

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.

Hi Team ,

I wanted to customize the result generated from Test studio. Kindly guide me a way.

Regards,

Prajna

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. 

using 2022.2.804.0

Hi,

Given I do not enable the Chrome extension or I run in Chrome Headless mode,

When I attempt to access the url https://make.powerapps.com

Then I get the following Network error

{"error":"invalid_request","error_description":"AADSTS9002327: Tokens issued for the 'Single-Page Application' client-type may only be redeemed via cross-origin requests.\r\nTrace ID: 2dec4c79-8808-4b00-b13c-c2dc348e0000\r\nCorrelation ID: 5624ddba-63af-4883-9855-1669b2228f77\r\nTimestamp: 2022-10-19 19:16:52Z","error_codes":[9002327],"timestamp":"2022-10-19 19:16:52Z","trace_id":"2dec4c79-8808-4b00-b13c-c2dc348e0000","correlation_id":"5624ddba-63af-4883-9855-1669b2228f77"}

Please advise.

Sometimes customers want to be able to run their test with the browser launching in a special mode (e.g. incognito mode, custom/specific user profile, etc.). If the customer could add custom command line parameters to be used when launching the browser they could accomplish this.

Hello,

I tried to use Headless mode and see that it doesn't work with clipboard. The part of my test scenario is click on button "Copy to clipboard" on the page and check the copied text. Nothing is copied in headless mode. 
Can you help me?

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. 

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.