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.
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..
During the trial period of Test Studio, by each start of Test Studio or Visual Studio there is a prompt window to continue the trial or activate a purchased license.
The license prompt window of the Test Studio plugin (part of the DevCraft Ultimate package as well) in Visual Studio 2019 start window prevents typing in the following native VS windows - Create project and Clone/Checkout code.
I. Change how Visual Studio 2019 starts:
1. Open any existing project in VS 2019
2. Open Tools-> Options-> Environment -> Startup
3. Select any of the other listed options in the dropdown on the right - Most recent solution or Empty Environment.
II. For the cases when DevCraft Ultimate is installed and the Test Studio plugin is not the current focus of evaluation.
1. Disable the Test Studio extensions.
2. Open any existing project in VS 2019
3. Open Extensions -> Manage Extensions -> disable the following extensions:
In the case when a custom layout is set and the Project explorer pane is hidden on the left side of Test Studio project, there is no indication if a new test is added in the project.
It will be very helpful if the Project Explorer pops up to indicate that adding the test was successful.