Test Studio supports adding a single custom base test class in the project. If one more base test class is defined and listed in a test code-behind file, the coded steps will be listed as empty and will not show the option to choose any of the methods in the test class.The steps will be still executed, but no changes can be applied within Test Studio (only in VS).
because I want many test sharing the same OnAfterTestCompleted(), instead of adding it to each test, I created new class:
using....
namespace test_studio_tests
{
public class CustomWebAiiTest : BaseWebAiiTest
{
public override void OnAfterTestCompleted(TestResult result)
{
// some code to be executed
}
}
}
and then all the tests to inherit from this new class
public class TestClass : CustomWebAiiTest
instead of Base one as they did so far. in TS project keep compiling, but then all the tests have extra icon and coded steps are not recognized anymore. in the meantime in VS2022 with TS plugin, all is recognized and keep working without any issue.
Once I have the browser up and running I don't need to start from 'Log onto URL'. Hence my high partial test run use.
I may be only running part of a test, but when the test is 500 steps its cumbersome to highlight the section I want to run, and where to stop.
It would be much easier to set a breakpoint, run the part of the test I need, and stop midway.
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;
Support for VS Community Edition
Building the find expressions for elements in HTML during recording respects the Identification Logic: http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/project-settings/identification-logic.aspx That isn't the case when Test Studio builds chained expressions though (e.g. it cannot find an Id or Name to build direct expression thus locates a unique parent element to include in the find logic. http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/knowledge-base/project-configuration/usingchainedfindexpressions.aspx In this case TS respects the Id or Name only and not the rest of the attributes (including custom ones). It will be nice if the chained find expressions building algorithm is extended to respect the preset identification logic as well.
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 you execute a test list in CI environment with the ArtOfTest.Runner.exe, there is no option to publish the results to the storage server (if you have setup a storage server).
It will be great to have this option, so we can view the results in the Executive Dashboard.
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.
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).
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.
A picture is worth a thousand words...
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.