Under Review
Last Updated: 15 Apr 2020 10:33 by ADMIN
Joseph
Created on: 14 Apr 2020 12:24
Type: Bug Report
0
Setting Test Property DataRange on a data driven web test causes Visual Studio to crash

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)
1 comment
ADMIN
Elena
Posted on: 15 Apr 2020 10:33

Hello Joseph,

Thank you for contacting us with details for the encountered error - we managed to reproduce the same and the case will be transferred to the developers team. You can follow this item to get updates on its progress. I am pleased to know that there is a workaround you can use until the issue is resolved. 

In addition and as a small token of gratitude from our side, I have granted your Telerik account with 500 bonus points. 

Thank you once again for your cooperation. 

Regards,
Elena
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.