Details and project for reproduction provided internally
Open a project in Test Studio and you'll notice the following flag which causes customer's confusion: [07/27 13:29:22,Telerik.TestStudio.Desktop.exe(12952:1)] First trace message from process 12952: "C:\Program Files (x86)\Progress\Test Studio\Bin\Telerik.TestStudio.Desktop.exe" False "C:\Users\ittodorov\Documents\Test Studio Projects\TestProject132" ======> /trial
Steps to reproduce: 1. Use Run->To Here against Chrome or Firefox. 2. Once the recorder is attached immediately hit the Pause button. Expected: The recorder is paused. Actual: The recorder is displayed as paused but it actually still records steps.
The sample application throws an exception when trying to automate it. A sample app and project are shared internally to reproduce the issue.
Chrome cannot be started with the required by Test Studio arguments when the "Application Identity" service is enabled in Windows 10 and as a result cannot record or execute tests with Test Studio. It will be beneficial to investigate the case on our end and identify if there is anything we could improve or at least document the known issue. A workaround could be to either disable that service or to add an exception for Chrome in an AppLocker rule to exclude it from the respective GPO.
Client`s Custom application has issue locating elements during execution against Chrome and FF. However, IE executes test successfully.
It would be useful to be able to set the value of a variable directly instead of expecting the result of another step.
Be able to execute a code method as a pre-execute action before the http request is triggered. This method should be built-in into the http request step and have access to the properties of the http request and be able to modify them. A use case example would be signing the http request based on its metdhod, url or other properties. (On behalf of Joe Phillips)
An exception is flooding the application log for a remote execution machine. The customer has two machines - one (win7) is execution only and the other (win 10) hosts the scheduling service and TS as well. Despite the exceptions the execution is successful. It would be good to investigate if we could find a solution for the faulty exceptions and if we could handle these. Details shared internally!
Executing the following code in Chrome does not work: ActiveBrowser.Actions.InvokeScript("document.getElementById('elemenID').click()"); the behavior is the same with the following workarounds: Element.InvokeEvent(ScriptEventType.OnClick); Element.Click(); More details are provided in the internal description.
Test Studio is not recording in <input type="tel"> inputs using JS Browsers. Locate an html using <input type="tel"> and try recording using Chrome or Firefox Problem: values are not recorded. Workaround: Use Internet Explorer for recording such inputs, the execution works as expected
Make a change to Test A, but don't save. Make a change to Test B, but don't save. Revert Test A to the server version. Navigate back to Test B & note that the red checkmark displays next to the test name. Open Test B & note that the pending change was wiped out. A warning message should be displayed to advise users that any unsaved changes will be wiped out if they revert a test to the server version.
Currently if you use a verify step on a <table> element, if the verify fails, you get "Expected count does not match" as an error message for failure information. I think this message should also include a line saying what the expected verified count was, and (or at the very least) an indicator of what the count was that the step failed to. Various things could cause a count to be wrong, and I believe that knowing what the count was at the moment that step failed, would help greatly in debugging these failures.
When using specific find logic for an anchor element there is a problem to locate the proper element during test execution. Steps to reproduce and access to the application are in the internal description.
There is out of memory exception generated when Run - To Here is applied to a step close to the end of the scenario. Steps to reproduce and access to the application are in the internal description.
It would be very beneficial to be able to see all of the failures from my project on a single screen, with from/to date parameters too, and be able to report on failure by type as well.