bwennekes's avatar
bwennekes
New Contributor
7 years ago
Status:
Implemented

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.

  • bwennekes's avatar
    bwennekes
    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.

  • bwennekes's avatar
    bwennekes
    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!