Currently Test Studio Execution extension allows to get the duration only of the overall test in the OnAfterTestCompleted() method.

Extend the functionality and include the option to get the duration of each separate executed step. 

Steps to reproduce: 

1. Use Chrome without extension, or headless mode.
2. Use the press key combinations Shift+End and Shift+Home in a coded step and be sure to set focus to a text field. 
   

   ActiveBrowser.Desktop.KeyBoard.KeyPress(Keys.Shift | Keys.End);
   ActiveBrowser.Desktop.KeyBoard.KeyPress(Keys.Shift | Keys.Home);

Expected: The combination selects the text in the field

• if the cursor is at the begining of the line use Shift+End;
• if the cursor is at the end of the line use Shift+Home;

Actual: The cursor only moves without selecting the text. 

Workaround: Use the key combination Shift+A to select the text. 

Steps to reproduce: 

1. Record the steps to select time from a radDateTimePicker component. 
2. The recorded step is 'datetimepickerclock: select time ''.'
3. Convert it to code.

Expected: The  code is compiled and executed as expected.

Actual: The converted code produces compilation error: 

[ Compiler ]
15:57:58 'ERROR' > C:\TestProject1\WPFTest.tstest.cs(55,104) : error CS1061: 'FrameworkElement' does not contain a definition for 'SelectTime' and no accessible extension method 'SelectTime' accepting a first argument of type 'FrameworkElement' could be found (are you missing a using directive or an assembly reference?)
15:57:58 'INFO' > Build Failed

Workaround: Cast the element like this: 

Applications.WPF_Demosexe.Telerik_UI_for_WPF_Desktop_Examples.PARTClockDatetimepickerclock.CastAs<Telerik.WebAii.Controls.Xaml.Wpf.DateTimePickerClock>().SelectTime("1:00 PM");

Steps to reproduce: 

1. Create a test list with 4 tests.
2. Each test executes more than 300-350 steps in overall because it is data driven.
3. Run the test list remotely/scheduled.
4. The generated result is uploaded in the Storage database and is visible in the Test Studio Results tab. 
5. Open the Executive Dashboard and try to open the runs for the same test list. 

Expected: The test results to be displayed.
Actual: The view is empty with the message: "There are no test results for this run."

Workaround: Split each test into a separate test list.

Log on the machine where the Executive Dashboard is hosted shows below error.

Telerik.TestStudio.ResultsServer.exe(7192:313),Error] CloudStorageRepository`2.ExtractItemsFromResponseAsync() : Error getting entity: Telerik.TestStudio.Interfaces.Storage.IStorageDocument`1[[ArtOfTest.WebAii.Design.Repository.LightRunResultSingleTestTransport, ArtOfTest.WebAii.Design, Version=xxxx, Culture=neutral, PublicKeyToken=xxxx]], from url: http://xxxxx/v1/results?includeDeleted=xxx&skip=xxx&take=xx&schema=xxx
Telerik.TestStudio.ResultsServer.exe(7192:313),Error] CloudStorageRepository`2.ExtractItemsFromResponseAsync() :
{"Message":"An error has occurred.","ExceptionMessage":"Command aggregate failed: Sort exceeded memory limit of 104857600 bytes, but did not opt in to external sorting. Aborting operation.

A custom web app requires key pad authentication to log in and this uses an extension in chrome/edge.

Test Studio does not allow signing in because the chrome being opened by Telerik does not allow me enable extension.

I have tried this for edge and chrome and it doesn't work. 

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. 

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.

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. 

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

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. 

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!