cancel
Showing results for 
Search instead for 
Did you mean: 

Saving without property values

Saving without property values

To extend the composite project functionality and improve the way ReadyAPI’s XML-files can be version controlled I would like an option to save without property values. Ideally this option can be enabled/disabled for properties defined at Test Step, -Case, -Suite and -Project level with a checkbox.

 

Currently there is only the option to ‘discard values on save’, which is only available on Test Step level. Discarding values on save can be quite cumbersome if you need the values making changes/corrections while still wanting to save often. This could mean that you need to rerun the whole project after a change is saved, which in my case may take more than half an hour.

 

At this time I’m still using the ‘discard values on save’ option by lack of alternatives. This also means that all properties in the project must be defined at step level, the only place where this option is available. This in turn means we cannot use functionality like the ‘Run Test Case’ Test Step as this uses properties on Test Case level, which is a real shame.

 

In my opinion just running and saving the ReadyAPI project should not change the project XML. As this currently does happen it creates hundreds of changes and merge conflicts without any functional changes in the ReadyAPI project.

8 Comments
Staff

There's a new project level property in ReadyAPI v2.3 - "Save Properties Between Sessions"

https://support.smartbear.com/readyapi/docs/testing/properties/about.html#save-properties

 

 

Does that meet your requirements?

 

New Contributor

@GillerM

I noticed this new feature in the 'What's New in ReadyAPI 2.3' already. It does seem that this will solve the above mentioned problem, though a bit less flexible than the suggested solution.

 

Hopefully my IT department will roll out this version soon so I can start working with it!

New Contributor

@GillerM

Finally I have ReadyAPI 2.3.0 available at my workplace. Unfortunately the new functionality is different from how I hoped it would work (the documentation seems correct though).

 

Setting 'Save Properties Between Sessions' to false resets the values after each run, which makes debugging and finding out where something went wrong after the run a real pain. So this creates a new problem. If there's something I missed here please say so.

 

For now this seems to 'break' more than it fixes and thus it is not a solution to the problem. The problem being: (properties with) run data should not be saved as this creates merge conflicts. But run data should be available for debugging.

Contributor

I fully support this feature. See my post on the SOAPui PRO forum that also describes my problem regarding the lack of this feature:

https://community.smartbear.com/t5/SoapUI-Pro/GIT-Integration-Prevent-merge-conflicts-Property-value...

New Contributor

I fully support this feature too! This is something which is missing from ReadyAPI and makes collaborating with team members difficult. I hope this is solved in the next version as it is causing issues with git, especially when rebasing with master. 

Contributor

Was a bit disappointed to not see this feature in 2.6, while being the TOP idea from the users base for quite some time. Fingers crossed for 2.7 ...

Let me stress that this feature not only would facilitate collaboration, but also just proper version control of the test project. After a day of working adding/editing/updating/deleting stuff I'd like to visually see what exactly was changed. Now I see (in GitExtension) ALL my xml files changed without any clue what specifically changed besides the (run-time) properties. So to write a proper git commit comment is a pain. I often have to revert/switch to different versions of the API code, so to be able to get the correct GIT commit makes this a real burden.

Occasional Contributor

I support any new feature which enables better, more insightful version control for team collaboration. 

Especially concerning the committing of only relevant changes.

Contributor

I also support any new feature which enables better, more insightful version control for team collaboration. 

Especially concerning the committing of only relevant changes.