When I run my test that requires a button click event it works fine. However, when that same test is run from test list, it does not - the web page remains the same, with the visible button not being clicked.
Weird, this only seemed to happen after upgrading to 2022.1.215.0
Steps to reproduce:
Expected: Successful execution.
Actual: The test fails on the verification step and reports that the value of the KendoInput is null.
Additional note: If the verification is added for the input control (instead of using the KendoInput), it is executed as expected.
The Kendo Angular Multiselect control is not covered with the built-in translators.
It will be very useful and consistent if such translator is added in Test Studio.
A picture is worth a thousand words...
Allow the ArtOfTest.Runner to publish the results to the Executive Dashboard. There they can be seen by members of the team, who do not have Test Studio installed.
Make it possible for the ArtOfTest.Runner to use multiple execution machines. Distribute the test list execution to other execution servers.
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).
We have a large PDF (60+ pages) and try to verify certain content on specific pages. During the recording process some elements are captured with TagName and TextContent and others with TagIndex. In this scenario TagIndex is not reliably, because the document is large and the elements change dynamicaly.
One solution is to update the element's find logic manually on all elements that use TagIndex, but this is very time consuming.
Another option is to use coded step to find the target element by TextContent and verify it.
When the Scheduling server is not added during installation, the Configure button in Test Studio will be greyed out (disabled). It will be helpful to add some kind of tool tip or note about this.
The solution is to modify the existing installation of Test Studio and add the Scheduling Server feature to the installation.
Allow users to add custom arguments when executing tests against any of the supported browsers.
This includes the Chrome Headless execution, which always defaults to en-EN language argument for example and you can't change it.
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.
We need to be able to verify the text in dialogs in different browsers.
The current solution is in code, but is not stable due to browser structure changes -> https://docs.telerik.com/teststudio/advanced-topics/coded-samples/html/verify-dialog-text-chrome
It will be helpful to have an element, which is defined based on another element. This is similar to chained find expression, but instead of defining the parent element with its find expression, add the ability to reference an already recorded element in the project as a parent one. Then add find expression for the child element.
As a result it seems that the translators for Kendo Angular Input and TextBox components are, currently, not backwards compatible with the previous versions of these controls.
It will be great to fix these so that the latest Test Studio can be used for testing web pages built with previous versions of Kendo Angular controls.
A specific coded steps test cause Chrome to be closed when trying to perform a partial run using Run->To Here.
The coded step before the navigate one is starting a proxy to log the traffic.
Sample project is provided internally.
Http requests' responses with content-encoding type 'br' cannot be decoded in Test Studio load testing. This results in the inability of using these responses to generate dynamic targets to cover the proper load test run.
Workaround: Modify the traffic for a load user profile by removing the 'br' encoding type. A third party Chrome extension can be used for this modification.