There is a dialogbox in WPF app to which the recorder toolbar gets attached. When the highlighting is enabled for this window no of the elements get highlighted.
The workaround is to use the DOM explorer tab in the Advanced Recording Tools to locate the desired element and build the desired step that way.
Details for the dialogbox and app shared internally!
Using the default Startup Args when configuring WPF test are not applied correctly.
The workaround is to use the startup arguments set for each test configuration.
There is no option in Test Studio recording capabilities to add a step which sets value for the WPF RadSlider control. It will be useful to have such similar to the WPF slider control.
The workaround is to set this in a coded step like this:
// Accepts values from 0 to 1
Applications.SliderTestexe.MainWindow.Item0Radslider.Value = 0.25;
Although the actual image files are with good resolution and are smooth, when displayed in the Failure Details Images tab they are blurry.
It will be great to display the images better.
Steps to reproduce:
Expected: The references are added with relative path starting under the project root.
Actual: The project root is included in the relative path.
Hello Progress Support,
I wonder if we can have "Bind data" applied on the "String Length" in "Generate random string" step?
Thank you for your help.
Regards,
Lisa
Hello,
Currently when I create a Git repo and connect Test Studio it creates default branch called "master".
Would it be possible to make it consistent with good practice and Git standard and rename it to "main" in the next version of Test Studio?
Can this be added as feature request please.
Thank you,
Max
When generating videos for the test runs from a test list, the output video files uses the name of the test only. There is no indication which is the test list from which this test was executed and when having multiple runs and videos it is difficult to relate these with the generated results.
It will be useful to generate the names of the videos from a test list in a way to correspond to the test list name and particular run.
Currently the exported result contains extended details only for the failed steps. If there is a warning for a step - like the warning that the element was found only by image, this can be only seen in the Test Studio result file.
Extending the HTML exported result to show the step warning details will be very useful for anyone who review this type of result (attached in an email after a scheduled run, for example).
Currently the Test Studio CLI runner AOT.Runner.exe allows outputting the results in junit format (other than xml and html).
Add the option to output the results in NUnit format.
Enhance Test Studio recording and execution options with the ability to prompt the user whether to deny or allow permissions to their geo location.
The app i'm testing may popup a dialog in Edge to ask the user to know their location.
However when i try to record the test using Edge i don't see this popup. I just see an error thrown by the app that says the user denied Geo Location.
When i access the app with edge outside of Test Studio i do get prompted.
Currently Test Studio built-in connection to Git repository is covered for the straight scenario for authentication.
Enhance the options for connecting to Git using authentication via proxy.
Add the option for radButton to verify if enabled in the offline step builder.
Steps to reproduce:
Expected: The option for verify if enabled step to be available.
Actual: The option is not available.
Currently if the value used for a filter starts with #, the comparison operator is automatically converted from 'is exactly' to 'matches this regular expression'.
So, if one needs to use URL fragment (starts with #) for element identification, for example, that # needs to be escaped.
The workaround to use will be to change the comparison operator with 'contains' and use the fragment portion without the # sign.