2011.1.502 & .511 - Function Evaluation Disabled errors

7 posts, 0 answers
  1. Peter
    Peter avatar
    1 posts
    Member since:
    Nov 2010

    Posted 17 May 2011 Link to this post

    Hey all,

    I just tried installing build 2011.1.502 & .511 but when I attempt to debug in VS, I'm plagued with "Function evaluation disabled because a previous function evaluation timed out. You must continue execution to reenable function evaluation." errors.  This was a rare occurrence in previous builds.  Is there any sort of work around to this issue, as I really need to debug some issues with upgrading to this version.

    Thanks.
  2. Cody
    Admin
    Cody avatar
    3354 posts

    Posted 18 May 2011 Link to this post

    Hello Peter,

    We are not aware of any specific issues or changes to the product that could cause this behavior. What sort of application are you trying to test (HTML, Silverlight, WPF)?

    Could you also double check that you do see a difference in the behavior of the different versions of Test Studio by re-installing the older version (perhaps on a separate machine or a VM) and make sure it does not exhibit this problem. I just want to verify this isn't being caused by a change in your application that happened to coincide with upgrading the version of the tool.

    All the best,
    Cody
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Peter
    Peter avatar
    1 posts
    Member since:
    Nov 2010

    Posted 27 May 2011 Link to this post

    Hey Cody,

    I'm testing a Siverlight Application.
    I just re-installed WebAii_Testing_Framework_2010_3_1421_FREE_EDITION and I can debug / watch / expand properties of my variables perfectly.

    I then re-installed Telerik.Testing.Framework.2011.1.511 And then upgraded to Telerik.Testing.Framework.2011.1.520 and as soon as I try to expand it, I receive the Function Evaluation disabled errors.

    Something as simple as:
    TextBlock tb = Application.Find.ByName<TextBlock>("myTextBlockName");

    hovering over tb, and then trying to expand it while debugging in VS will cause these errors.
  4. Alexey Ivanov
    Alexey Ivanov avatar
    45 posts
    Member since:
    Sep 2009

    Posted 31 May 2011 Link to this post

    I experience such issues when I test html pages, no Silverlight.
    This happens mostly when using Actions.InvokeScript and with other methods which require execution of javascript in the browser.
    Almost impossible to debug tests :(
  5. Cody
    Admin
    Cody avatar
    3354 posts

    Posted 31 May 2011 Link to this post

    Hi Alexey Ivanov,

    Thank you for the report. I have been able to reproduce this problem. I have filed a regression bug here.

    Best wishes,
    Cody
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  6. Peter
    Peter avatar
    1 posts
    Member since:
    Nov 2010

    Posted 01 Jun 2011 Link to this post

    Thanks Cody for acknowledging this as a bug and reporting it.  Is there any ETA on if it's going to be fixed for the next internal release?  As it stands now, in order for me to debug I have to:
    - uninstall my current version
    - re-install an older version
    - refactor a bunch of code (change some settings to Web settings, change Find.ByText to Find.ByTextContent, change radio button SmartClicks to Checked, etc)

    then do the reverse when it's time to check-in my code.  So this is a very important fix for me.

    Thanks
  7. Cody
    Admin
    Cody avatar
    3354 posts

    Posted 01 Jun 2011 Link to this post

    Hi Peter,

    All I can say for certain is that a fix for this problem will nit make it into our Service pack release coming in about a week. We already have planned out what it will include and this bug did not come in in time to make it onto that list.

    Beyond that we first have to diagnose what's causing it, figure out how much code has to be changed to fix it, schedule those changes in our workflow, before we can come up with an ETA. All our bugs go through this process.

    Kind regards,
    Cody
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top