Forum Discussion

JDR2500's avatar
JDR2500
Frequent Contributor
2 months ago

Execution Plan group/subgroup names now limited to 30 chars??

I just tried to create a new subgroup in our Execution Plan using a descriptive name.  We've been doing this for years.  Now with 15.72.60.7 I get an error indicating the names can't exceed 30 characters.  Anyone else seeing this?

As you can see, this was not a problem when I created the group immediately above the new one using an earlier version of TestComplete.

I also have no idea where "Load Group" in the message is coming from.  

I'm regretting 'upgrading' to15.72.

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3

    It's a bug in the latest version, and the "Load Group" is most likely referring to the "Add New Load Group" button

    If you modify the .mds file to have long names, it loads fine.

     

    • JDR2500's avatar
      JDR2500
      Frequent Contributor

      Thanks for investigating and confirming the problem!

  • Hassan_Ballan's avatar
    Hassan_Ballan
    Regular Contributor

    I suggest you create a support incident. Load group is for load testing. I don’t have latest version to try.

    Are old names still executing currently?

    Editing old names also gives same error message?

    • JDR2500's avatar
      JDR2500
      Frequent Contributor

      Yes, items in groups with long names will still execute. 
      However, attempting to edit one of the existing longer names results in the same error message.

      I don’t have latest version

      That was a good call on your part.

  • JDR2500's avatar
    JDR2500
    Frequent Contributor

    Update:  Smartbear support reproduced the issue and suggested downgrading to v15.71 to work around it until there is a fix available.

    I was able to reproduce the issue on my end after adding a group to an existing project suite.

    I went ahead and created an escalation with our operations team regarding this dialog prompt and group character limit. I'll update you here once I receive any new details from the development team. In the meantime, I would suggest downgrade TestComplete to the previous version to work around the issue.