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
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.
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;
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:
Expected: The compilation is successful.
Actual: The compilation fails with the mentioned error.
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.
The step gets successfully executed but fails with the following exception:
Failure Information:
~~~~~~~~~~~~~~~
ExecuteCommand failed!
InError set by the client. Client Error:
Cannot read property 'toggle' of undefined
BrowserCommand (Type:'Action',Info:'NotSet',Action:'InvokeJsFunction',Target:'ElementId (tagName: '',occurrenceIndex: '-1')',Data:'$("th:eq(1)").data("kendoFilterMenu").popup.toggle()',ClientId:'663fc963-6051-4044-9dfb-ce01ca15339d',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'Cannot read property 'toggle' of undefined')
InnerException: none.
Workaround: Record the click step to open the filter without using the Test Studio translator, or in other words against the span element directly.
Hi Support,
I am facing the below issue with the Product.
We were able to isolate the issue and it is reproduce able on Bing.com.
Basically, the “ Run to Here “ or “Test as a Step” functionality , they both pretty much do the same job.
Taking you to the previously recorded steps to continue with further recording.
Steps to Reproduce-----
Create Test#1
Go to Bing. Com and record few tests and close the browser.
Now, Right Click on the last recorded step and Select Run -To Here.
At this point, try to record and capture the Elements.
When you use either of the above mentioned functionality, the Recording and Elements capturing would stop working.
We were able to reproduce this from mine and one of my co-worker's laptop.
This is the same issue what I am facing with our Application (few weeks back Test studio has a release, could be related to build as it was working when i downloaded the tool initially)
Please let me know if you need any additional details from me.
Thanks,
Shubha
Steps to reproduce: 1. TS version is R1.2016.1117 2.. The problem page contains a table which is nested in another table (both have the same ID) but if the ID is searched in the recorder it is not found at all although the element exists. During the investigation was determined that both tables are under div element which is not loaded in the recorder DOM tree. Details shared internally.