Forum Discussion

PeterG's avatar
PeterG
New Contributor
7 months ago

clone TestSuite fails when there are more project with the same name

Today I was trying to clone TestSuite between projects.

It was not possible in one, specific case, when:

  1. the project was already in Workspace, but closed
  2. the project was in Workspace for a second time, but as open

I suspect that it tries to clone it to closed project, as it's first in Workspace projects tree, and then it fails.

It would be great to fix it.

  • Hi PeterG 

    The possible solution is to rename one of the projects with the same name.
    This avoids confusion and ensures the TestSuite is cloned to the correct open project.

    Since SOAP UI might be attempting to clone the TestSuite to the closed project based on its position in the workspace tree

    Hope this helps - Happy to help further!!
    Thank you very much and have a great one!
    Warm regards

  • Humashankar's avatar
    Humashankar
    Champion Level 3

    Hi PeterG 

    The possible solution is to rename one of the projects with the same name.
    This avoids confusion and ensures the TestSuite is cloned to the correct open project.

    Since SOAP UI might be attempting to clone the TestSuite to the closed project based on its position in the workspace tree

    Hope this helps - Happy to help further!!
    Thank you very much and have a great one!
    Warm regards

    • PeterG's avatar
      PeterG
      New Contributor

      Hi Humashankar

      Thank you for this workaround. Yes, it works, but when I have tens or hundreds of soapUI projects in my workspace, it is hard. I remove each with the same name and re-import it.

      Anyway, it would great if SmartBear can add logical condition to try to add cloned TestSuite only to project that is open or based on project reference of item selected in drop-down menu.

      Best,
      Peter

      • Humashankar's avatar
        Humashankar
        Champion Level 3

        Hi PeterG 

        You are right, renaming every project with the same name would be challenging - we can recommend this to a future enhancement.

        Regards