Extracted text from one element (PPSR FSID), used binding to set in another element (PPSR Search using FSID), Test failed because FSID could not be found, on closer inspection the set text had 2 different characters than the extracted text S instead of 8 and T instead of 7 (sorry snip is so wide) Have attached zipped code.
It is not possible to check if the visibility of certain element is "Hidden". Currently Test studio allows verification for "Visible" and "Collapsed", but not for "Hidden".
Please add "Hidden" to the options.
Currently the new design of the step failure details is only available for Web tests. Please add this feature for WPF tests, as well.
When we execute a WPF test, there are no suggestions and additional details in the Test pane. We need to open the step failure details window, by clicking on the red "X" of the failed test step.
During a recording session with enabled Hover Over Highlighting, the context menu with recording options disappears before we can use it. This make it hard to add verification and action steps or locate the element in the DOM tree.
This only happens in one of the ComboBox dropdown controls.
Currently it is not possible to change the image for recorded Image Verification step. In our case, the WPF application under test changes its state, when it is not on focus and it is not possible to capture the correct image.
We need to be able to change the image after the step was recorded.
Currently the Edit Test List window has fixed size, which causes usability issues when the test names are long, or when they are in a folder.
Make the window resizable and remember its previous size when I open it again.
Test Studio scheduled runs sometimes start browser in the background and it loses focus. Due to that the test steps are not executed correctly and the test fails unexpectedly.
This does not happen when running the test or test list locally.
Make it possible to choose whether or not to group the results from all iterations and provide average time, when exporting the results.
I have 20 iterations of the same steps and it will be helpful to see the average time for each step.
The TextFromImage verification step extracts the wrong text in some scenarios.
One example is that the number "8" can be recognized as "3", when it is at the beginning of the element (text). Other times, the word "learn" is not extracted correctly from a sentence.
When you edit the "Wait for ExistsNot" step as coded step, the generated code does not reference the target element from the Pages. Instead, it creates a fixed find logic from the current state of the element in the Elements Explorer.
The issue is that when the find expression for that target element changes, the coded step fill not be updated.
Currently we have an Angular select control and we are experiencing troubles with the automation. The value is visibly selected but it is not used further in the application. It appears that the "OnInput" event is not triggered during the selection.
We have found a workaround, which is to trigger that event in a coded step:// This is necessary to trigger event listener
Not able to install Telerik Test Studio
=== Verbose logging started: 4/16/2021 10:47:39 Build type: SHIP UNICODE 5.00.10011.00 Calling process: Local\Temp\7zSCA0634CB\ProgressWebInstaller.exe === MSI (c) (94:58)
The Test Studio Recorder is not attaching to the browser when I start recording.
I have two test lists, one is configured to be executed against Firefox and the other - against Internet Explorer.
When I run the two test lists form the Test Explorer in Visual Studio, all tests from both test lists are executed against the browser of the first test list. The execution browser changes if I rename the test lists in a way that the second one is not the first.
When Daylight Savings Time ended on November 6, our scheduled tests started running an hour earlier than scheduled. I had to "edit" each schedule (without actually changing any settings) and save in order for the time in the "TimeToRun" setting in the job details file to adjust for the time change. It would be nice if this could happen automatically. Or maybe add a right-click option to for updating the time or something.
When there is a conflict in a source controlled project, Test Studio should output more details about the conflict. That will make it easier to track and resolve, as multiple users work in the same project.
Currently the output pane does not specify anything for the conflict.
When you open a test, that was created in Test Studio and has coded steps, for the first time in Visual Studio, the coded steps are not linked to the methods in the code behind file. They appear as blank and you need to select the methods again.
This behavior is specific for Visual Studio and how it loads the files in the solution. The workaround is to double click on any of the coded steps to open the code behind file. That will restore the connections in every coded step in this test.