The specific page and the frame, which is not identified from Test Studio, uses a Salesforce component called ForceAlohaPage and it seems there is a custom implementation for the frames in this component. These are not visible in the Windows.Frames collection, which Test Studio uses under Manager.ActiveBrowser.Frame. 

When you execute a test list in CI environment with the ArtOfTest.Runner.exe, there is no option to publish the results to the storage server (if you have setup a storage server).

It will be great to have this option, so we can view the results in the Executive Dashboard.

Test Studio 2020.2.910 

The list of recent projects keep a deleted entry on restart.

Steps to reproduce:

1. Open the Test Studio Welcome view and choose a project to remove from the Recent project list.
2. Open any other project and close it exiting Test Studio. 
3. Start Test Studio again - the removed project from Recent items is listed again. 

If a test in a test list has compilation errors, it should not be possible to schedule it for execution. There is an error pop-up when I click on the Schedule Test List button, but no error if I right click on the test list and schedule it from there.

Please improve the behavior of the context menu in the Test Lists tab.

The Image verification and OCR steps do not work for WPF tests.

Those steps are simply not added to the test with the latest release 2020.R2.

Telerik Test Studio has the options to Add a, Bind (to an existing), or Unbind from a data source.

However, the VS Test Studio plug-in only has Add and Unbind.

It would be nice to be able to do everything within Visual Studio.

We should be able to add a verification which verifies that a string is “not exactly”.

The steps added for the ASP.Net Ajax controls RadInput and RadButton automatically scrolls the target element to top of the page. In the case when there is a static header on the page, the element gets scrolled under it and the actual action cannot be performed correctly. 

The workaround to use is to add the input or button element from the DOM tree and manually add a Click or Enter text step, enable 'SimulateRealClick' or 'SimulateRealTyping' and change the ScrollType property to scroll the element to the center of the page instead to top. 

There is no direct method in the Testing Framework, which can be used to scroll the RadGanttView control in WPF app. 

It will be useful to explore such implementation.

It would be useful to support the generated output file additionally in a human-readable format (markdown/html), when it comes to automated API testing.

We (dev/qa team) would like to attach the file to the story as documentation of the test case. So that the product manager or other colleagues (without license access) can easily take a look at the covered cases. 

The current xml output (sample attached) already provides a good overview and could be extended with background information in some places (for example <action>).

Trying to open a RadComboBox with

var csBox = Window.Find.ByName<RadComboBox>(ComboBox);
csBox.EnsureClickable();

csBox.SelectItem(1);

Observing the automation shows we are waiting no time for dropdown to open and I am getting exceptions claiming there are no items in the list.

The cause is related to the fact that the public void WaitDropDownAnimation(int millis) method of Telerik.WebAii.Controls.Xaml.Wpf.RadComboBox is not working as expected. 

Workaround: You can use Window.Find.ByType<RadComboBoxItem>().Wait.ForNoMotion(milliseconds); before selecting the item from the dropdown.

There are times where test studio throws this exception described in http://feedback.telerik.com/Project/161/Feedback/Details/121035-path-too-long-on-backup-problem

[04/24 11:48:37,Telerik.TestStudio.RemoteExecutor.exe(5092:133),TestStudio] AutomationHostState.StoreToFile() : EXCEPTION! (see below)
     Situation: AutomationHostState.StoreDomOnDisk
     Outer Exception Type: System.IO.PathTooLongException
     Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
     HRESULT: 0x800700CE (Official ID (if app.) = 2147942606, Error Bit = FAILED, Facility = FACILITY_WIN32, Code = ERROR_FILENAME_EXCED_RANGE)
     Call Stack:
          at System.IO.PathHelper.GetFullPathName()
          at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
          at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
          at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
          at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
          at ArtOfTest.WebAii.Design.AutomationHostState.StoreToFile(String filePath, Object value, String traceMethod)

[04/24 11:48:37,Telerik.TestStudio.RemoteExecutor.exe(5092:133),TestStudio] AutomationHostState.StoreImageBytesOnDisk() : EXCEPTION! (see below)
     Situation: AutomationHostState.StoreImageBytesOnDisk
     Outer Exception Type: System.IO.PathTooLongException
     Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
     HRESULT: 0x800700CE (Official ID (if app.) = 2147942606, Error Bit = FAILED, Facility = FACILITY_WIN32, Code = ERROR_FILENAME_EXCED_RANGE)
     Call Stack:
          at System.IO.PathHelper.GetFullPathName()
          at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
          at System.IO.Path.GetFullPathInternal(String path)
          at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)
          at ArtOfTest.WebAii.Design.AutomationHostState.StoreImageBytesOnDisk(String projectResultsPath, String fileRelativePath, String expectedImageRelativePath)

There was a MSDN blog by Kim Hamilton that suggested a possible solution to this issue.  http://blogs.msdn.com/b/bclteam/archive/2008/07/07/long-paths-in-net-part-3-of-3-redux-kim-hamilton.aspx

Please see if this exception handling is feasible.

When I close the Remote Desktop connection, the Test Runner on my VM reconnects to the Windows session successfully, but it does not set the correct resolution. 

It seems to default to a base resolution and not the one from Change Console Resolution settings in the Test Runner.