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
AlumniHi Guys,
Our Dev Team should investigate this. I’ll get back to you once I hear something from them.
AlumniHi 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.
Thanks, I figured that was exactly the problem as well--that's why I included my possible cause in the details.
However, before I posted the issue, I already tried a couple things within soapUI, hoping that it would refactor the IDs but it didn't solve this problem.
Can you ask the Dev's about their recommended way to branch a project within soapUI?
Here's what I already tried within SoapUI, to no avail:
1. Right-Click on Project --> Save As
a. This saved the project with a new name, but didn't re-factor any element IDs
2. Right-Click on Project --> Export
a. This made a new copy of the project, but it didn't re-factor any of the element IDs, so also didn't help
Ken
