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..
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.
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).
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:
When using the visual studio plug-in, if you update coded files (anything ending in .tstest.cs), when you open your project back up in TS standalone IDE, the changes you made to any given coded file will not automatically be detected so you must open up every .tstest file corresponding to the .tstest.cs files you changed in visual studio, and only then will the IDE see the changes
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.
The imported test was created with data binding. After I imported the test successfully, I did not get/have the xls that was used in the other project. The test execution fails due to the missing data source file.
GetComputedStyle() for hyphenated computed style against Microsoft Edge does fails with the following error:InnerException: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
We are using telerik testing framework for Automation testing. Currently we are executing our scripts in a client VM using TFS builds. Now we would like transform to Docker Execution. We couldn't get the direct solution from any forum for Telerik Testing framework and Docker integration. So please help us on identifying the docker image for Telerik testing framework, so that we will make use of it and we will create a container for the same to run our test scripts in docker vm. Any websites/links related to this topic would be helpful for us.
At this point it is possible to run a WPF application with arguments only as a workaround - starting a separate process in a coded step as given in this example. It would be more useful if this feature is implemented when configure the WPF app in the test.