A popup with "End of Central Directory record could not be found." error shows up when I try to add a custom step from the step builder.
When I restart Test Studio, the test works fine.
After installing my DevCraft package, my keyboard has limited functionality, when trying to create a new project/solution in Visual Studio 2019. I am able to use "space" and "backspace" keys, but not letters and numbers.
Uninstalled Test Studio Dev or disabling Telerik.TestStudio extension and I have full keyboard functionality on screen for creating a new project in Visual Studio 2019.
As a workaround I am able to use CTRL + V to paste any text from my clipboard.
Android mobile app cannot be configured with Android Gradle plugin 3.4.2 and no test can be recorded against that.
Ability to add multiple And/Or conditions in IF bracket
Recording using existing Chrome session is not available
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").
Steps to reproduce:
1. Open an Enter password step and expand in the step pane
2. Set the encrypt property
Expected: All fields with the actual text entered should be masked with *
Actual: If the step is expanded the actual text entered field does not change its value.
Note: Reopening the test fixes the visual glitch.
Add NTLM authentication in Test Studio for APIs or some kind of workaround.
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.
When using a builtin step for checking rowscount of a table that uses "greater than" or "less than" it fails even though it should not.
"Equals" works fine.. but if I use any other TableVerificationType than "equals", then it fails.. unless if I convert it to a coded step.
So to reiterate: If I convert the step to a coded step then it works.
We have several test projects that now have failing tests because of this.
Attached test project that showcases the problem.
When the element's find expression fails to find the element it should log in the execution log, that alternative method of verification is used.
The Wait for Exists step does not log the usage of image verification, even though the find expression fails.
The behavior with click step is as expected and the log is correctly generated.'17-Jul-19 14:10:30' - 'Pass' : 2. Click 'BtnKSubmit'
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..