Hi
I tried adding a validation to check on a hyperlink's RenderSize value.
The generated test code is as shown below:
// Verify BlaBlaHyperlinkbutton.RenderSize 'Equal' '{107 16 False}'
Assert.AreEqual(ArtOfTest.WebAii.Silverlight.UI.StructSize.Parse("{107 16 False}"), new ArtOfTest.WebAii.Silverlight.UI.StructSize(Pages.AgencySuite0.SilverlightApp.BlaBlaHyperlinkbutton.RenderSize), "Property did not satisfy constraint");
The problem is that BlaBlaHyperlinkbutton as no RenderSize property.
Please advise.
thanks
I tried adding a validation to check on a hyperlink's RenderSize value.
The generated test code is as shown below:
// Verify BlaBlaHyperlinkbutton.RenderSize 'Equal' '{107 16 False}'
Assert.AreEqual(ArtOfTest.WebAii.Silverlight.UI.StructSize.Parse("{107 16 False}"), new ArtOfTest.WebAii.Silverlight.UI.StructSize(Pages.AgencySuite0.SilverlightApp.BlaBlaHyperlinkbutton.RenderSize), "Property did not satisfy constraint");
The problem is that BlaBlaHyperlinkbutton as no RenderSize property.
Please advise.
thanks
1 Answer, 1 is accepted
0
Hi Dudi,
this appears to be a bug. I've logged it and you can track its progress here:http://www.telerik.com/support/pits.aspx#/public/test-studio/7404
500 Telerik points added to your account for discovering this issue.
It seems that you converted a regular step to a coded step and that led to the issue. My suggestion would be to refrain from converting this particular type of step into code until we've managed to release a build containing a fix for this. If you haven't done so already check out the section on coded steps in our online documentation:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/coded_steps.aspx
Kind regards,
Stoich
the Telerik team
this appears to be a bug. I've logged it and you can track its progress here:http://www.telerik.com/support/pits.aspx#/public/test-studio/7404
500 Telerik points added to your account for discovering this issue.
It seems that you converted a regular step to a coded step and that led to the issue. My suggestion would be to refrain from converting this particular type of step into code until we've managed to release a build containing a fix for this. If you haven't done so already check out the section on coded steps in our online documentation:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/coded_steps.aspx
Kind regards,
Stoich
the Telerik team
Vote for Telerik Test Studio at the Annual Automation Honors Voting!