The tests execute as expected but upon checking the logs the variable names are no longer displayed and instead I am only able to see testStudioBase64EncodedVar.

This change will make debugging issues much more difficult in the future

BlazorTextArea records a KendoAngularTextBox step. Upon execution the step doesn't enter the text as expected. 

To workaround this, you can disable the KendoAngular controls group from the Project Settings -> Translators -> HTML and re-record the step. 

Add the option to start quick execution of tests in Headless mode from Visual Studio.

Currently it is available from the Select Execution Browser window, but if you have selected a preferred browser this window is skipped.

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.

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.

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

On the Executive Dashboard, the columns are all fixed sized, the problem with this is that it gives very little space for test and test list names and makes it difficult to view the naming.

Please provide a way to resize or view the names easily.

Really excited to have a dashboard to present to the team now

Is there anyway to configure the number of Tests that display from within a result?  Right now it only looks like 5 is what is the default, that requires quite a big of pagination.

Telerik does not support test studio assemblies in .net standard and does not have a test runner in .net core. Considering all of our Azure DevOps and container agents are running linux we will not be able to use the tool.

Please add this feature to your product.

How can I change the size of the element suggestion pane? I can't seem to click and drag it, and I'd like to see more than two or three options.

Currently there is only a scroll that can be used to view all options.

The step to verify an element for enabled/disabled step cannot be data-driven. The 'Verify element exists' also does not provide a binding option.

However, the 'Verify isVisible' step can be data driven with true/false values for the isVisible property. 

It will be useful and helpful to unify the behavior and allow data binding for isEnabled and Exists verification steps.