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.
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.
We've posted about this before, tickets and forum.
https://www.telerik.com/account/support-center/view-ticket/1621768
Attached is the log of a different failed scenario. Unlike ticket 1621768, there is no execution delay (hardcoded) before the error. To be sure, we get what seems to be random failed tests that run successful more often than not in most prior runs. What seems constant is that our test lists will encounter errors in an automated Azure pipeline run (if we then run that same pipeline manually, it's usually successful).
Is there something we can do to the environment that we are running the test lists, the settings or something of that nature? Maybe some way to "prime" the environment?
Note, our license is under bwhite@mlhc.com
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.
Error upon compilation is related to the Pages.g.cs file where all elements are listed with their find expression.
12:38:44 'ERROR' > C:\Users\dpruteanu\Test Studio Projects\After_reinstall_3-27-24\Pages.g.cs(229,108) : error CS1003: Syntax error, ',' expected
Steps to reproduce:
Expected: The compilation is successful.
Actual: The compilation fails with the mentioned error.
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.
public static DesktopFind WaitForDesktopAppWindow(DesktopApplication desktopApp, string strWindowsName)
{
return desktopApp.WaitForWindow(strWindowsName, delay, 60000).Find; //with a delay of 700
}
fails if COMException is thrown.
Expected is to handle that exception and wait for the set timeout.
Support for VS Community Edition
When generating chained find expressions Test Studio always uses the id tribute for the parent element and it doesn't take into account the actual order of attributes.
Then, if you completely remove the id from the find logic list settings, the generated find expression uses only TagIndex for the target element and no chained find expression.
Generating this type of expressions need to be revised.
Example shared internally!
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.
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:
Version 2023.3.1115.
Test list logging option is not saving log in specified location from test list settings.
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.
When sorting tests from the test list result panel, the same sorting is applied to the steps in every test from the test list when drilled down.