TestStudio returns 0 for the number of tabs in a Kendo Angular TabStrip control. The behavior is reproduced on the demo page of the control - https://www.telerik.com/kendo-angular-ui/components/layout/tabstrip/tabs

Test Studio version is 2021.2.809.0

1. Navigate to https://demos.telerik.com/kendo-ui/autocomplete/index
2. Enter text in the autocomplete input and select the filtered country from the dropdown. 
3. The recorded steps are KendoInputValue enter text and KendoListBox select item and these are correctly recorded.
4. Execute the test. 

Expected: The steps should enter the text as it is listed in the step and select the country. 

Actual: The text from the KendoInputValue enter text step gets entered with capitol letters, although these are small letters in the step. If there is a capitol letter in the step, it is not sent at all. 

Example: KendoInputValue enter text 'Great Britain' actually enters 'REAT RITAIN'

Test Studio 2022.1.215

Steps to reproduce: 

1. Record a test to navigate to https://www.telerik.com/kendo-angular-ui/components/inputs/textbox/

2. Enter some text in the field and select it with ctrl+A.

3. Press the Del button to delete it.

4. Execute the test.

Expected: The text should be removed with the step to press Del.

Actual: Del is entered as text in the text field.

The is an issue with Connect to pop-up step, when the new tab immediately has a Logon dialog.

The Logon dialog handling takes priority and is handled before the Connect to pop-up step is executed. As a result, the identification and connection to the new tab is failing and Test Studio does not have access to any of its elements.

This issue is reproduced in Chrome and Edge Chromium browsers.

Chrome Headless Failed to Select ByText when text value includes apostrophe.

The workaround is to select ByIndex or ByValue, if the value does not have an apostrophe.

Using the Telerik.ApiTesting.Runner.exe to execute API tests cannot output results in junitstep format. It throws an error if using the -f junitstep option when running tests or test suite:

I am presently working on a government contract and on a virtual machine they can not give me administrator rights because of resent hacks a policy.

Can I please get a contact number and email address that I can have the system administrator talk to and try to get this problem fixed because I am a contractor

and have been working with them to get this fixed and we have not been able to resolve this and because of this no testing is getting done for automation.

Please help I have been using telerik for over 5 years and this is the first time I have had this problem

Thank you

Donna DeVries

ddevries.ctr@ntia.gov

bigdjdv@cox.net

402-672-2898

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.

The tests and test lists are visible in the Test Explorer and can be run the first time you open the Test Studio project in Visual Studio 2019. After any changes or rebuilding the solution, the tests and test lists disappear from the Test Explorer.

The issue is related to the latest version of Visual Studio 2019 and is recognized in build 16.10.2.

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.

Navigate to the application under test and click a link that opens in a new tab. Then, click within the new tab to redirect it to a new URL and close the tab. 

The result is that the Close pop-up window step is successful, but the tab is not closed. This results in issues with the following steps in the test scenario.

If using the coded solution to launch a WPF app for testing (sample code listed here), the ArtOfTest.Runner crashes.

Workaround: Replace the line
ActiveApplication.Quit(); 

with
ActiveApplication.MainWindow.Window.Close();

Implement Headless browser support

1. A Test Studio project in Visual Studio.

2. Add an independent element in the project - an element, which is not tied to a step and is added through the highlighting menu while recording (Add element to Repository). 

3. Try to rename this element.

Expected: To be able to enter new name for the element.

Actual: Visual Studio crashes and exits the project.

Workaround: The same element can be renamed in the Test Studio Standalone project. 

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