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.

Hi guys,

We're using Telerik Testing Framework for automation and running tests primarily against IE browser and since we have security policies enforced on clients, tests started to fail more often with ApplicationException on start.

After some investigation we found that in LaunchNewBrowserInstance() function in Core.Manager has hardcoded timeout to 5000, which is not enough now for IE to respond. As you can see in the code below, everything is using 'timeout' variable except 'Connector.Attach(ref handle, 5000);' - it uses hardcoded timeout to wait:

internal static object LaunchNewBrowserInstance(
      int timeout,
      ProcessWindowStyle windowStyle,
      string pipename,
      string url)
    {
      string str = string.IsNullOrEmpty(url) ? "about:blank" : url;
      try
      {
        ProcessStartInfo startInfo = new ProcessStartInfo()
        {
          Arguments = (InternetExplorerActions.MajorVersion >= 8 ? "-nomerge " : string.Empty) + str,
          Verb = "open",
          WindowStyle = windowStyle,
          ErrorDialog = false,
          FileName = "iexplore.exe"
        };
        System.Diagnostics.Process process = System.Diagnostics.Process.Start(startInfo);
        TraceInfo.Framework.ReportProcessLaunched(process, startInfo);
        IntPtr handle = InternetExplorerActions.WaitForIEFrameFromProcess(process, timeout);
        TraceInfo.Framework.WriteLine("Attempting to attach on IE frame (HWND={0})...", (object) handle);
        Connector.Attach(ref handle, 5000);
        System.Diagnostics.Process currentProcess = System.Diagnostics.Process.GetCurrentProcess();
        int num = currentProcess.Id;
        if (currentProcess.ProcessName == "ArtOfTest.Runner")
          num = InternetExplorerActions.SafeGetParentOrCurrentId(currentProcess);
        Connector.InjectCode(handle, InternetExplorerActions.ArtOfTestPlugin, pipename, num.ToString(), true, timeout, "");
        return (object) null;
      }
      catch (Exception ex)
      {
        throw new ApplicationException("Exception thrown attempting to launch Internet Explorer. Please make sure Internet Explorer is properly installed and you are able to launch it.", ex);
      }
    }

This is likely the cause, why our increased timeout settings are ignored and test fails shortly after start, even if we increase timeouts significantly. Visually, it looks like IE is doing some background job and is not responsive for some period of time and 5 seconds is not enough to wait. So, could you change the code to respect 'timeout' instead of using constant number?

We've been using Telerik Testing Framework for a long time already and from time to time had this issue, but workaround it by catching exception, killing browser and trying to launch it again. But now that trick is not helping anymore, the majority of tests fails with this exception on start.

This fix is really simple and will save us a lot of time, trying to invent some new solution to make IE more responsive on start.

Thanks,

Oleksii

There is a Load test with two requests:
Request 1: In the response there is a token with the following string GZYQmiG0FWePB/ZvbtjN8mOpMQ5qL0R9u/EEoxUt812HF7eHlRBNG

This string is extracted in a custom dynamic target and its target is the second request as URL query.
Request2: URL is <host>/connect?token=GZYQmiG0FWePB/ZvbtjN8mOpMQ5qL0R9u/EEoxUt812HF7eHlRBNG

The issue is the "/" in the URL query is not encoded, which leads to an error.

After the latest release of Chrome and Edge Chromium browser (version 87.x) the behavior of Close pop-up Window step is changed. Instead of closing the browser tab, the whole browser is closed and the execution stops. 

As a workaround for this issue, you can downgrade the browser to version 86.x or use Firefox or Internet Explorer temporarily.

I am doing a Wpf test.

1. Connect to a script by right clicking on it and click record.

2. Program launches. Stop recording by clicking on Print Screen keyboard key.

3. Close the  program and recorder closes.

The recorder stays connected: 

So if I try to record or execute a script I get this message:

It looks like when I stop the recording and then close the program the recorder does not disconnect.

I have to completely shut the program down and restart test studio so I don't get the above error message.

Version: 

CaptureBrowser() functionality does not work as expected with Firefox browser on Windows 10 version 2004. The captured image shows only the browser frame and and white contend of the browser.

Set a manual step anywhere after the first step and before the last step of the sequences to test. When the manual step is reached the dialog that is rendered will be black text on a black background and it is hard to read the isntructions. 

I have enabled the "Reconnect to console on disconnect" option in my execution server. When I close the active remote connection, I noticed that the resolution changes and this causes my tests to fail.

Please find a solution for this.

Show MongoDB service's status in the Configure Test Studio Services window in MongoDB tab. If it is running, it should indicate it in a similar way as the Storage and Scheduling services.

Currently, only when you apply the service settings, it is started and that is shown in the status bar. If I close the Configure Test Studio Services window and open it again, that information is missing again.

With Find Logic for an element, sometimes the Find Logic uses Text Content on initial element recording and other times the Find Logic uses ID. 

I request for functionality in Test Studio to prioritize what logic is actually used in the Find Logic.  Generally speaking on the applications I have used Test Studio to automate testing, there are elements that has specific text content on a page.  These elements start out with their Find Logic to have TextContent since I think that is the most unique identifier about them.  But as TextContent is concerned, there is a possibility of change of text on that element.  So I would target the element with the ID of the element or the ID of a parent element and then use tagindex to be specific.

After initial recording, I put in the extra time to modify the Find Logic to fit my need.  

If an element does not have an Id, but the element has a direct parent (only 1 level above) element with an ID, use that parent element and then the additional find logic for specific element over using TextContent. 

Having this functionality of Find Logic prioritization will hopefully provide a general consistency to improve my user experience.  

When entering a value into an input field of type="password", would it be possible to have the IsPassword property automatically turned on so the the password would not be displayed while recording? Currently the password will be seen in Test Studio when recording, until the IsPassword property is turned on. When recording during demonstrations, it would sometimes be nice if the password wasn't displayed.

There are some instance (e.g. find and connect to a ClickOnce WPF application) where it's desirable or necessary to launch the WPF application outside of Test Studio's normal launch process, then, using an API call, instruct the framework to connect to and automate (i.e. run the rest of the test) the already running WPF process. This would be most useful for ClickOnce applications because the install path frequently changes. Using code it can find and launch the WPF application. If there was an API call provided, the coded step could tell Test Studio to connect to it and run the test normally from that point on.

Currently for IE recorder we can configure the highlighting options on a project level, for the color, thickness and menu hold time. We should hook up the new Chrome and Firefox recorder to use the same configuration for consistency.

Please add clear browser cache button so it can insert a test step that is clearing the cache. Currently we do have clear cookies button and if you would like to clear the browser's cache you should use coded step only.

Currently our feature to send out automated emails is too difficult to use. It's badly documented and there's no indication that it even exists in the UI unless you know exactly where to look for it. I heartily suggest:
A) We move this to the cloud and we have it always be present in the UI and useable without any special configuration
B) We remove this feature

Currently our website lists it as a big part of the product and this is far off from how difficult it is to use.

I prefer having the properties window for the selected test docked somewhere in Test Studio.

On this page:
http://docs.telerik.com/teststudio/user-guide/knowledge-base/test-execution/using-baseurl.aspx

We talk about how to use BaseUrl for the NavigateTo steps and the iframe nodes. What we're missing is how to adjust the Connect to Popup steps so that they too work in multiple environments.

The screen shots on this page are very out dated:
http://docs.telerik.com/teststudio/user-guide/troubleshooting_guide/test-execution-problems/chrome/cannot-execute-in-chrome.aspx

Please add a submenu to the 'Run to Here' which allows you to select the browser to be used instead of the default specified.

The only way to select a different browser for 'Run to Here' is to go into 'Project settings -> Browsers' and remove the default browser.

If a compatible compatible database engine is not installed, no sheets are listed to select from when data binding a test. See ticket 881911 for the symptoms and solution.