Under Review
Last Updated: 06 Apr 2020 08:50 by ADMIN
Created by: Larry
Comments: 0
Type: Bug Report
1
The "Description" column is missing, when I export the test results from the Results tab in Excel. This was previously working on Test Studio 2019.1 and earlier versions. It looks to be a regression, so please take a look and resolve it.
Under Review
Last Updated: 06 Jul 2020 15:03 by ADMIN

Using the Telerik.ApiTesting.Runner.exe to execute API tests cannot output results in junitstep format. It throws an error if using the -f junitstep option when running tests or test suite:

[ERROR] Not supported test results format
Parameter name: junitstep
Under Review
Last Updated: 15 Apr 2020 10:33 by ADMIN

On a data driven web test, setting the DataRange property to the example "SingleRow" causes Visual Studio 2017 to crash.  I have three rows of data in a data table that are bound to specific steps of my test.  I was attempting to limit execution to only one row temporarily. Using SingleRow or 'SingleRow' causes Visual Studio 2017 to crash with the following stack trace as found in Windows Event log.  I was able to successfully use '1:1' or ':1' as a work around.

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
   at ArtOfTest.Common.Design.ProjectModel.TestBase.set_DataRange(System.String)
   at ArtOfTest.Common.Design.ProjectModel.TestBase.SetUserProperties(ArtOfTest.Common.Design.ProjectModel.TestBaseUserProperties)
   at ArtOfTest.WebAii.Design.ProjectModel.Test.SetUserProperties(ArtOfTest.Common.Design.ProjectModel.TestBaseUserProperties)
   at Telerik.TestStudio.Web.Toolbar.previewTestProperties_Click(System.Object, System.EventArgs)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(System.Object, System.EventArgs)
   at System.Windows.Forms.ToolStripButton.OnClick(System.EventArgs)
   at System.Windows.Forms.ToolStripItem.HandleClick(System.EventArgs)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(System.Windows.Forms.MouseEventArgs)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(System.EventArgs, System.Windows.Forms.ToolStripItemEventType)
   at System.Windows.Forms.ToolStripItem.FireEvent(System.EventArgs, System.Windows.Forms.ToolStripItemEventType)
   at System.Windows.Forms.ToolStrip.OnMouseUp(System.Windows.Forms.MouseEventArgs)
   at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
   at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.ToolStrip.WndProc(System.Windows.Forms.Message ByRef)
   at ArtOfTest.WebAii.Design.UI.VsToolStrip.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
Under Review
Last Updated: 12 May 2020 11:43 by ADMIN

See the screen shot.

There are two annotation markers. For some reason, a "MouseClick:LeftClick" will appear, as it should, but then it sticks there, even as 10 or 12 other steps execute and their annotations come and go. Sometimes another MouseClick:LeftClick will appear and the old one will go away and then the new one will stick. But this does not happen every times. Sometimes a new MouseClick:LeftClick annotation comes in and goes away and the old one is still hanging around.

This happens will almost all of my scripts.

Is it because some of the mouse clicks are from recorded steps and some are from code steps? This is just a guess.

Under Review
Last Updated: 23 Jun 2020 09:52 by ADMIN

Dear Support,

The version I am using is not listed below: 2020.1.403.0

I am noticing an inconsistency when using the Replace Element feature i.e. the attributes selected are not respecting the priority set in the Settings - Find Logic (Html) screen.

Please refer to screenshots attached.