Won't Fix
Last Updated: 02 Sep 2024 12:23 by ADMIN

I ran a test list through 'Schedule TestList' using "Run locally" scheduling setup and i received an email with html attachment. When i open the html I can see the actual and expected screenshot are missing.

Unplanned
Last Updated: 28 Aug 2024 13:49 by Marek
Created by: Marek
Comments: 0
Type: Bug Report
1
Unable to record a click step on a dropdown in specific customer's WPF app
Won't Fix
Last Updated: 21 Aug 2024 11:01 by ADMIN

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. 

 

Completed
Last Updated: 15 Aug 2024 11:21 by ADMIN
Created by: Jim
Comments: 3
Type: Bug Report
0
I updated a few days ago 2023.1011.1.
I highlight and run a set of steps. When it ends, the Steps Pane scrolls to the bottom.
Since I may have hundreds of steps, remembering where I was and scrolling up to get there is time consuming.
Please fix this.
Completed
Last Updated: 15 Aug 2024 11:21 by ADMIN

 public static DesktopFind WaitForDesktopAppWindow(DesktopApplication desktopApp, string strWindowsName)
        {
      return desktopApp.WaitForWindow(strWindowsName, delay, 60000).Find; //with a delay of 700

}

fails if COMException is thrown.

Expected is to handle that exception and wait for the set timeout. 

Completed
Last Updated: 15 Aug 2024 11:21 by ADMIN

Error upon compilation is related to the Pages.g.cs file where all elements are listed with their find expression. 

12:38:44 'ERROR' > C:\Users\dpruteanu\Test Studio Projects\After_reinstall_3-27-24\Pages.g.cs(229,108) : error CS1003: Syntax error, ',' expected

Steps to reproduce: 

  1. Testing WPF app which has quotation mark in the name of the window.
  2. Record some steps for a scenario.
  3. Convert any step to code, or insert a coded step.
  4. Compile the project.

Expected: The compilation is successful.
Actual: The compilation fails with the mentioned error. 

Completed
Last Updated: 15 Aug 2024 11:21 by ADMIN

Steps to reproduce:

1. Add the following line in coded step 

ActiveBrowser.Desktop.KeyBoard.KeyPress(System.Windows.Forms.Keys.Alt);

2. Execute the test in extensionless/headless mode

Expected: Test should pass
Actual: Test fails and the following error is thrown in the log:

ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
InError set by the client. Client Error:
Protocol error (Input.dispatchKeyEvent): Invalid 'text' parameter
BrowserCommand (Type:'Action',Info:'NotSet',Action:'RealKeyboardAction',Target:'null',Data:'keyDown#$TS$#LMenu',ClientId:'59E9D6A07CE0CD30467ED59AEC375281',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'Protocol error (Input.dispatchKeyEvent): Invalid 'text' parameter')
InnerException: none.

   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Headless.HeadlessKeyboard.PressOrReleaseKey(Keys key, Boolean release)
   at ArtOfTest.WebAii.Win32.KeyBoard.KeyDown(Keys code, Boolean delay)
   at ArtOfTest.WebAii.Win32.KeyBoard.KeyPress(Keys code)
   at Regressuib2024R2.Alt.Alt_CodedStep() in C:\Users\ittodorov\Documents\Test Studio Projects\Regressuib2024R2\Alt.tstest.cs:line 57

Completed
Last Updated: 15 Aug 2024 11:21 by ADMIN

For a specific page (shared internally)

1.Record a navigate step
2. Execute the recorded test in headless/extensionless

Expected: The test should pass
Actual: The navigate step fails and the following exception is thrown in the log:

Failure Information:
~~~~~~~~~~~~~~~
ExecuteCommand failed!
BrowserCommand (Type:'Information',Info:'IsReady',Action:'NotSet',Target:'null',Data:'',ClientId:'8DBC801FE56B61C67C029E52C7448B0C',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')
InnerException: System.TimeoutException: Timed out waiting for command to be handled
   at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId, Int32 timeout)
   at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)

Workaround: Use a coded step to increase the ExecuteCommandTimeout like this: 

 Manager.Settings.ExecuteCommandTimeout=120000;

Completed
Last Updated: 15 Aug 2024 11:20 by ADMIN

Using the default Startup Args when configuring WPF test are not applied correctly. 

The workaround is to use the startup arguments set for each test configuration. 

Completed
Last Updated: 15 Aug 2024 11:20 by ADMIN

A click step might throw ArgumentNullException when executed against a pop up that is in the process of being opened.

Details:

Exception 'System.ArgumentNullException: Value cannot be null.

Parameter name: source
   at System.Linq.Enumerable.Where[TSource](IEnumerable`1 source, Func`2 predicate)
   at ArtOfTest.WebAii.DesktopAutomation.DesktopFind.GatherResultsFromXPathSearch(String xPath, Int32 maxDepth, DesktopFindExpressionGroup group, List`1 roots, List`1 results)
   at ArtOfTest.WebAii.DesktopAutomation.DesktopFind.<>c__DisplayClass26_0.<AllByExpression>b__0()
   at ArtOfTest.WebAii.DesktopAutomation.DesktopFind.RetryIfNullOrEmpty[T](Int32 retries, Int32 retryDelay, Func`1 findFunc)
   at ArtOfTest.WebAii.DesktopAutomation.DesktopFind.AllByExpression(DesktopFindExpression expression, Int32 maxDepth, Int32 maxRetries, Int32 retryDelay)
   at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.FindElementInternal(IAutomationHost targetHost, FindExpressionElement expression, Region region, String& error)
   at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.FindTargets(IAutomationHost targetHost, AutomationDescriptor baseDescriptor)
Completed
Last Updated: 15 Aug 2024 11:20 by ADMIN

Details for the application shared internally! 

Elements that are visible on the page cannot be directly located in the DOM. Even if find expressions are manually adjusted to match the correct elements, the steps fail to execute as expected because the elements are considered not visible. 

Declined
Last Updated: 25 Jul 2024 07:37 by ADMIN

When initiating a 'Record' on a web test in Test Studio, the relevant browser (Edge Chromium, but Firefox and Chrome have been tried) is launched and URL navigated to, but only a single step is recorded:

Navigate to : '/'

 

We are attempting to record regression tests against a custom web app. Steps are recorded fine if navigating to (for example) google.com and typing in a search query.

 

Please let me know what further information I can provide to narrow this down.

Unplanned
Last Updated: 16 Jul 2024 14:53 by Max

I noticed that in the recurring scheduled test the settings do not persist if we select " Only on error..." .

It defaults back to "Always".  I would expect it to remember the original setting. 

Unplanned
Last Updated: 11 Jul 2024 12:00 by HemoSonics
In WPF I have been able to connect to an application using the new Connect to Application Step, but then when I try to reconnect back to the original running application and run additional steps, it does not find the elements, and still thinks it is connected to the 2nd application that i connected to.

Example:

Running Test on App A,
Connect to App B and run more steps
Connect back to A to run steps, and the next step fails with an error that it couldn't find the element in App B.
Unplanned
Last Updated: 30 May 2024 11:31 by Naveen

Additional details shared internally!!! 

A workaround is to manually refresh the DOM tree so that it gets updated to the current state of the page.

During a recording session the refresh DOM option is available in the Advanced Recording Tools window -> DOM Explorer tab -> Toolbar options -> Refresh button. 

During test execution the refresh DOM option is available in a coded step - Manager.ActiveBrowser.RefreshDomTree();

While researching the case we also noticed that after some delay the DOM tree is refreshed automatically, so a delay step is also an option to be tried.

Declined
Last Updated: 30 May 2024 11:20 by ADMIN
Created by: Dominik
Comments: 1
Type: Bug Report
0

1. Edit a Test
2. Test shows * for pending changes
3. Can't find a ribbon button for saving the changes -> I can only use [CTRL]+[S]

Maybe you can add the button in the section "Edit" or as seperate big button before the "Edit" section?

Unplanned
Last Updated: 27 May 2024 11:07 by ADMIN

1. Record a test with elements that weren't in the repository
2. Move the element via Drag & Drop into an if-else case
3. Rename element in the TreeView on the left hand side

Normally the element name gets refreshed in the project and shows the correct name.
In an if-else case the name won't be refreshed.

Screenshot:

Unplanned
Last Updated: 27 May 2024 11:06 by ADMIN

1. start recording
2. enable hover over highlighting
3. switch window with [ALT]+[TAB]

After switching from WPF-Window into Telerik Teststudio the hover over highlighting is still active

Unplanned
Last Updated: 24 Apr 2024 11:33 by Marek

There is a dialogbox in WPF app to which the recorder toolbar gets attached. When the highlighting is enabled for this window no of the elements get highlighted.

The workaround is to use the DOM explorer tab in the Advanced Recording Tools to locate the desired element and build the desired step that way. 

Details for the dialogbox and app shared internally! 

Need More Info
Last Updated: 19 Apr 2024 09:31 by ADMIN

We've posted about this before, tickets and forum.

https://www.telerik.com/account/support-center/view-ticket/1621768

https://www.telerik.com/forums/telerik-test-studio-test-list-run-from-azure-pipeline-fails-when-triggered-by-a-build-completion-of-another-project

Attached is the log of a different failed scenario. Unlike ticket 1621768, there is no execution delay (hardcoded) before the error. To be sure, we get what seems to be random failed tests that run successful more often than not in most prior runs. What seems constant is that our test lists will encounter errors in an automated Azure pipeline run (if we then run that same pipeline manually, it's usually successful).

Is there something we can do to the environment that we are running the test lists, the settings or something of that nature? Maybe some way to "prime" the environment?

Note, our license is under bwhite@mlhc.com

1 2 3 4 5 6