Forum Discussion

kbw's avatar
kbw
Contributor
10 years ago

Defect: When Ready API opens, it auto-expands navigation pane items that were NOT opened previously

Whenever we open Ready API (any version), it seems to randomly open up items from multiple projects--this is the new "remember last opened" feature in Ready API.


However, these are items that were never opened in the first place.  We'll close Ready API with just a couple things in one single project expanded, all other projects completely collapsed. Yet, the next time we open, several projects will have items expanded.

 

The way this "feature" is supposed to work is that the only times that should be re-expanded are the actual ones that had been open at the end of your last section.

 

It's a waste of time because it clutters up the navigation tree and every time we have to go and manually collapse them all.

 

Possible Relation to Underlying Cause:

The extra projects that are expanded, but shouldn't be, are always older versions of whichever project that had been left open during the last Ready API session.  There is likely something about these projects that's confusing Ready API to make it think that it not only has to expand the actual one that was last being worked on, but also all of the older versions of the project too.

 

The way we manage our projects when there are new features in a given version of our app, is that we simply copy the entire soapUI project xml in the Windows file system, rename it and import it into Ready API, giving it a proper project name to reflect the version it supports.  For example, we might have a 7.5, 8.0 and 8.2 versions of a given soapUI project.

5 Replies

  • kondasamy's avatar
    kondasamy
    Regular Contributor
    10 years ago

    Yes, I have experienced this problem too! The feature is really good thought from SoapUI NG Dev team, but with few corrections as mentioned by @kbw, it would be an awesome one. BTW., neatly explained the problem! Kudos!

     

     

    Thanks,

    Samy

    • TanyaYatskovska's avatar
      TanyaYatskovska
      Icon for Alumni rankAlumni
      10 years ago

      Hi Guys,

      Our Dev Team should investigate this. I’ll get back to you once I hear something from them.

      • TanyaYatskovska's avatar
        TanyaYatskovska
        Icon for Alumni rankAlumni
        10 years ago

        Hi Guys,

         

        Our Dev Team suspects that this behavior can be related to the fact that you externally modify your project files. Please let me know if this is the case. Here is their reply:

         

        Every node at the navigator tree has its own unique ID. If you simply copy the entire XML SoapUI project file in the Windows file system, rename it and import it into Ready! API, then each node won't be unique at this project. Ready! API expands/collapses nodes by this ID. That is why users may have these strange results. We don’t recommend copy and rename projects externally (outside Ready! API). For this purpose, Ready! API has copy operations.

         

        We’ve failed to reproduce this behavior working with projects only in Ready! API. If a user has stable steps to reproduce this behavior, we need to know them.

  • kbw's avatar
    kbw
    Contributor
    10 years ago

    Hi Tanya,

     

    Has Dev replied to you on my last question, about how they recommend copying an entire project so that the internal IDs get re-generated for the new copy?

     

    I have found absolutely no way that Ready API supports copying an entire project and re-factoring all of the project's internal IDs.

     

    Thanks,
    Ken

     

    FYI, I have found one semi-work around, though it's clunky:

    1. Create a new empty project

    2. Save

    3. Remove the project from Ready API

    4. Open your empty project in a text editor

    5. Copy the project's ID  (e.g. <con:soapui-project [...] id="c3c5c38a-1d10-4c81-a390-6facdce7e3e2" [...] )

    6. In a text editor, open one of your existing projects that's affected by this defect

    7. Replace this project's ID with the one that you just copied from the new empty project.

     

    This isn't perfect, since all items under the projects still have the same IDs, but at least it gives the project itself a new ID and Ready API will stop expanding the project at the top level at startup.