Currently the chrome://settings/ page cannot be automated in Test Studio. Enable accessing this page to allow changing some settings during test run-time.
The scenario to cover is opening an embedded in the page PDF file instead of downloading it. The Test Studio calibration sets the browser's setting for PDF files to 'always download' and if the PDF is embedded it will nor be downloaded, neither opened.
Selected step in the test can be dragged and dropped in the same test only. Extend the functionality to be able to drag and drop the steps between the opened tests.
Currently there is an alternative to reuse the steps between tests - you can copy a step and paste it into another test. Choose between the step context menu options, or the standard keyboard shortcuts for these operations (Ctrl+C and Ctril+V). Select mulitple steps using the Ctrl and Shift keys along with mouse clicks for selection - selecting sequent items using Schift key and selecting non-sequent items with Ctrl key. The copy/paste/cut/delete actions also work for multiple steps selection.
Download dialog which is triggered from a new tab fails to be handled when running a test in Edge and Chrome extensionless mode.
Such download dialog is usually triggered with a link similar to this:
<a href="100MB.zip" target="_blank">Link to donwload</a>The download dialog looks like this:
.jpg){kind=avatar}
When trying to connect Test Studio project to Git source control the following error message appear:
The below snippet to find specific element fails to return the expected element. The Content is of the same element regardless of the "parent()" method.
var item = Find.jQuery()
.tag("div")
.classes(new string[]{"className"})
.contains(name)
.parent()
.first()
.Content;
Currently when running the all test suites from an API project, the run stops if there is a failure. There is no option to automatically continue the test execution and only mark the failed one. You can continue running the test suites one by one.
Enhance the options for running the API test suites and allow the execution to continue even if one suite fails.
Please add different way to make a user profile inactive rather than changing the Workload to 0 (zero)
Is there any way to view the result history of a single test that is part of a test list?
We run a test list each night and I can look at each nightly test list run and check individually but I'm looking for a more simple way to see the full history of a single test and how often it is passing or failing.
My rerun tests are passing but the reports are showing failed results.
I expected Test Studio reports to reflect the run results.
The use case is that the generated date is used to define an item in certain system with its creation time.
Workaround
Use the generated date variable in code and concatenate the prefix, then output the new value to a new extracted variable to use the next steps.
Test Studio results could be exported as interactive HTML files. Currently the result summary does not include details about the total number of rerun tests and the number passed tests.
It is a good idea to enhance the result summary to include this information.
Specific customer application requires double click to trigger an action. When running the test without extension, the double click is not executed as expected and the test fails on the next verification step.
Workaround Enabling the usage of extension for the browser (Chrome and Edge) resolved the misbehavior.
Additional details are shared internally!
Enhance the test results for distributed runs - there is no information which is the execution machine for each test in the case of distributed test list execution through the Scheduler on more than one executors.
It will be also nice to see the agent name in the Run Results Viewer dialog.