Save As scenario in SOAPUI
Hey there,
I've noticed what I believe to be an issue when saving a project under a new name. When I click the project name in the navigation tree and then right-click to save as I am given the option to save the project under a new name. This then creates a copy of the current project using the new name. But within SOAPUI the context remains the same.
I have a project called Proj_1. I start a new piece of work but choose to reuse an existing project as a starting point, (it has all my resources set up how I like them!). I open ProjX, click Save As and give it the name I'd like to use for the new project, Proj_2. Proj_2 is created but is not made active. As far as SOAPUI is concerned I am still working on Proj_1.
So what ends up happening is that I edit my older project with the changes I'd like to have included in Proj_2 - the only problem is it doesn't make the changes in Proj_2. Proj_2 isn't even open, it is infact making changes to my original project Proj_1.
Summary: I realise that this is a behaviour thing. It is a user experience I have grown accustomed to through years of use of MS products. Where, when I Save-As a Word document the Save-As version becomes the active one. So that I am now working in the new context and my source file is safe. This feel intuitive to me.It is also how millions of others would expect this scenario to work.
Could you guys triage this issue as it has nailed me many times. I always assumed it was due to my own fatigue that the issue happened. Latenight coding and too much coffee meant I was sure that SOAPUI would behave just the same as most other applications in the world. (try it on Notepad++ too - its not just M$ products that do this)
Do you think you guys could visit this scenario in a coming release. There is no reason why usability should take a backseat in a platform as brilliant as yours.
Cheers,
- Richard
I've noticed what I believe to be an issue when saving a project under a new name. When I click the project name in the navigation tree and then right-click to save as I am given the option to save the project under a new name. This then creates a copy of the current project using the new name. But within SOAPUI the context remains the same.
I have a project called Proj_1. I start a new piece of work but choose to reuse an existing project as a starting point, (it has all my resources set up how I like them!). I open ProjX, click Save As and give it the name I'd like to use for the new project, Proj_2. Proj_2 is created but is not made active. As far as SOAPUI is concerned I am still working on Proj_1.
So what ends up happening is that I edit my older project with the changes I'd like to have included in Proj_2 - the only problem is it doesn't make the changes in Proj_2. Proj_2 isn't even open, it is infact making changes to my original project Proj_1.
Summary: I realise that this is a behaviour thing. It is a user experience I have grown accustomed to through years of use of MS products. Where, when I Save-As a Word document the Save-As version becomes the active one. So that I am now working in the new context and my source file is safe. This feel intuitive to me.It is also how millions of others would expect this scenario to work.
Could you guys triage this issue as it has nailed me many times. I always assumed it was due to my own fatigue that the issue happened. Latenight coding and too much coffee meant I was sure that SOAPUI would behave just the same as most other applications in the world. (try it on Notepad++ too - its not just M$ products that do this)
Do you think you guys could visit this scenario in a coming release. There is no reason why usability should take a backseat in a platform as brilliant as yours.
Cheers,
- Richard
