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..
We use the Telerik Testing Framework to run our pre-release tests on our AJAX.NET solution. The newest version contains the MultiColumnComboBox. The problem is, that the Testing Framework is missing a wrapper for the new Control (as the other controls have).
Allow deserialization of dateTime values to strings instead of DateTime objects when extracting such with JSONPath.
When a dateTime value is returned in a JSON response ("2019-04-08T00:00:00") and a JSONPath expression is used to extract it from that response, Test Studio deserializes it to a DateTime object. This leads to losing its original format.
It will be useful to have the option to deserialize it in a plain string value.
Visual Studio behaves differently when using the PresentationCore.dll and on scaling different than 100% - here is some additional information about the Microsoft DPIHelper class.
Using this one somehow interferes with how Test Studio and the Testing Framework handles the different display scaling settings and causes some actions to be performed on wrong element.
Currently iOS Xamarin application can be configured to be testable on a Mac machine.
A good extension of the feature will be to add the ability to build the iOS application from Visual Studio on Windows machine.
Add Test As Step in Test Studio Mobile project. This will enable me to better organize the test scenarios and reuse already recorded tests.
The same feature is available in Web & Desktop projects.
It will be useful to implement handling the scenario where a page supports multiple files download in a sequence
- a prompt to decide whether to allow or block the multiple files download,
- download dialog steps to handle each of the files download location.
I have some databound parrent tests.
For these I have created seperate sheets in my excel, to ensure my part test are working i switch their databinding between the sheets to ensure them working in all environments.
Everytime i rebind a test the excel file gets corrupted! I have to restart the computer and then it works again… What is the fix for this?
I have attached an example of being unable to open the excel document!
Changing the DPI settings to 125%, for example, on Windows 7 causes troubles with the Desktop clicks when running tests against Chrome. The click is below or above the target element. Highlighting in record mode may also be affected.
Workaround: As a workaround the Desktop clicks (MouseClick() method) can be replaced with the Click() method, which works as expected. The alternative in a non-coded solution is to disable the 'SimulateRealClick' option for the click steps.
One of my element has the following find logic:
XPath is exactly //td/input[@title[contains(., 'End Date (Month Day Year)')]]
When I ran my script I got the error below:
Exception thrown executing coded step: 'Enter Leave Request To Date in 'LeaveRequestToDateText''.
'//td/input[@title[contains(. 'End Date (Month Day Year)')]]' has an invalid token.
I notice that the find logic expression displayed in the error message has a missing comma. Do you know why?
When used in code Wait.For() certain element's attribute state, does not respect the timeout set to wait.
Additional details shared internally.