When initiating a 'Record' on a web test in Test Studio, the relevant browser (Edge Chromium, but Firefox and Chrome have been tried) is launched and URL navigated to, but only a single step is recorded:

Navigate to : '/'

We are attempting to record regression tests against a custom web app. Steps are recorded fine if navigating to (for example) google.com and typing in a search query.

Please let me know what further information I can provide to narrow this down.

I noticed that in the recurring scheduled test the settings do not persist if we select " Only on error..." .

It defaults back to "Always".  I would expect it to remember the original setting. 

Details for the application shared internally! 

Elements that are visible on the page cannot be directly located in the DOM. Even if find expressions are manually adjusted to match the correct elements, the steps fail to execute as expected because the elements are considered not visible. 

Currently WPF tests always require an application to be configured and launched upon test start. So, one need to always use a dummy app when using the 'Connect to app' and 'Launch app' steps. 

Enable the WPF test configuration with the option to not launch an application - similar to the configuration experience for Desktop test. 

Additional details shared internally!!! 

A workaround is to manually refresh the DOM tree so that it gets updated to the current state of the page.

During a recording session the refresh DOM option is available in the Advanced Recording Tools window -> DOM Explorer tab -> Toolbar options -> Refresh button. 

During test execution the refresh DOM option is available in a coded step - Manager.ActiveBrowser.RefreshDomTree();

While researching the case we also noticed that after some delay the DOM tree is refreshed automatically, so a delay step is also an option to be tried.

1. Edit a Test
2. Test shows * for pending changes
3. Can't find a ribbon button for saving the changes -> I can only use [CTRL]+[S]

Maybe you can add the button in the section "Edit" or as seperate big button before the "Edit" section?

when I open TS -> Results -> 

lets say it's Wednesday, a noon, and I have daily runs. I see some already executed - marked as green or red, and some yellow tiles, from the future. When I try to check what is the PC node name where a single task (list) will be executed, I don't see that info on a tile directly. Moreover, when I go and edit it, I see settings for a frequency and time, in next step I see what is the name of list selected, but on the very next step, where all nodes are listed, nothing is selected. That looks like a bug. So, if I have 20 things scheduled, I need to rely on my own notes to be sure I edit correct task. The name of the PC is available only for already executed task. No idea why it's not visible for future runs. 

A click step might throw ArgumentNullException when executed against a pop up that is in the process of being opened.

Details:

Exception 'System.ArgumentNullException: Value cannot be null.

1. Record a test with elements that weren't in the repository
2. Move the element via Drag & Drop into an if-else case
3. Rename element in the TreeView on the left hand side

Normally the element name gets refreshed in the project and shows the correct name.
In an if-else case the name won't be refreshed.

Screenshot:

1. start recording
2. enable hover over highlighting
3. switch window with [ALT]+[TAB]

After switching from WPF-Window into Telerik Teststudio the hover over highlighting is still active

Steps to reproduce:

1. Schedule a test list with 'Rerun failed tests' option set to true. 
2. The project to upload to Storage needs to produce a compilation error upon execution. 
3. Check the test results.

Expected: The test list run does not execute any of the tests due to the compilation error and logs a failed test list result.

Actual: The test list run does not execute any of the tests due to the compilation error and logs a passed test list result.

Steps to reproduce:

1. Add the following line in coded step 

ActiveBrowser.Desktop.KeyBoard.KeyPress(System.Windows.Forms.Keys.Alt);

2. Execute the test in extensionless/headless mode

Expected: Test should pass
Actual: Test fails and the following error is thrown in the log:

ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
InError set by the client. Client Error:
Protocol error (Input.dispatchKeyEvent): Invalid 'text' parameter
BrowserCommand (Type:'Action',Info:'NotSet',Action:'RealKeyboardAction',Target:'null',Data:'keyDown#$TS$#LMenu',ClientId:'59E9D6A07CE0CD30467ED59AEC375281',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'Protocol error (Input.dispatchKeyEvent): Invalid 'text' parameter')
InnerException: none.

   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Headless.HeadlessKeyboard.PressOrReleaseKey(Keys key, Boolean release)
   at ArtOfTest.WebAii.Win32.KeyBoard.KeyDown(Keys code, Boolean delay)
   at ArtOfTest.WebAii.Win32.KeyBoard.KeyPress(Keys code)
   at Regressuib2024R2.Alt.Alt_CodedStep() in C:\Users\ittodorov\Documents\Test Studio Projects\Regressuib2024R2\Alt.tstest.cs:line 57

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. 

For a specific page (shared internally)

1.Record a navigate step
2. Execute the recorded test in headless/extensionless

Expected: The test should pass
Actual: The navigate step fails and the following exception is thrown in the log:

Failure Information:
~~~~~~~~~~~~~~~
ExecuteCommand failed!
BrowserCommand (Type:'Information',Info:'IsReady',Action:'NotSet',Target:'null',Data:'',ClientId:'8DBC801FE56B61C67C029E52C7448B0C',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')
InnerException: System.TimeoutException: Timed out waiting for command to be handled
   at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId, Int32 timeout)
   at ArtOfTest.WebAii.Messaging.Process.BrowserHostsProxyRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)

Workaround: Use a coded step to increase the ExecuteCommandTimeout like this: 

 Manager.Settings.ExecuteCommandTimeout=120000;

I need to export the contents of our test lists to a CSV, TXT or Excel file. There is no option other than exporting the generated results from a test list run. 

However I need to be able to export the tests in a test list before I get to the point of executing these. 

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!