StepType should be editable for any element, it will help user to update same step for different StepType if user want to add/update step quickly without recording or add from Step builder
Ability to create clone of Element just like Tests and then rename it including changing properties
This will allow user to add multiple elements on the single page too quickly
Recording using existing Chrome session is not available
Ability to add multiple And/Or conditions in IF bracket
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.
Test Studio has support for Xamarin.Android however, I've seen that projects created with Xamarin.Forms are not fully supported. Is there any plan to have this compatibility in the future (ETA) ?
Export a test list result to HTML and open it.
When you hover over the actual and expected images, they are zoomed. They are not visible enough and as a result it is hard to analyze them.
Please improve their resolution and visibility.
Currently you can find the ImageOnFailure in the project's Results folder under the unique test list's result folder (something like "Failing Test 132106926993112448").
Add NTLM authentication in Test Studio for APIs or some kind of workaround.
It would be useful to have the functionality to build the project from command line.
Currently scheduling a test list with getting the latest server version of the project is only possible if the source control repository is of the TFS version control type (Team Foundation Version Control).
It will be very useful to add the same functionality for Git source controlled projects.
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.
The Application we are using stopped the support for IE. So I have to switch to chrome to be able to connect to the DOM window of TEST STUDIO. Inorder to connect to the browser, I have to use "Run - To here" option and then connect to the browser. Then I Navigate to the Page where I actually want to do the recording and debugging.
But in IE browser, I have the opened instance already and then I can connect the recorder wherever I want. This is more easier way of recording and debugging and save time.
So, Could you please consider this feedback and add the option for "Attach to chrome" browser. Refer to Screenshots..