Forum Discussion

jrforeman's avatar
jrforeman
Occasional Contributor
4 years ago

How to prevent ReadyAPI from randomly changing how it stores empty XML elements?

Why does ReadyAPI change how it stores a blank XML tag from, say <con:properties/> to <con:properties></con:properties>   If I make one change and save, I may see many of these differences, whic...
diff
git
readyapi
source control
XML
  • jrforeman's avatar
    jrforeman
    3 years ago

    So the solution really is: You can't prevent it. Whenever you upgrade, the new version of ReadyAPI will do whatever it wants with regard to the empty XML fields... some versions will generate a beginning tag and end tag <tag></tag>, then the next version may decide to use the shortcut <tag/>, and the version after that may revert to the expanded <tag></tag> again, and there is nothing to be done but allow it. 😞

     

mkrausem's avatar
mkrausem
Occasional Contributor

Hi,

 

I decided for my team that everone has to use the same version (and with same configuration)

This was our "solution"

 

Kind Regards, Michael

jrforeman's avatar
jrforeman
Occasional Contributor
3 years ago

So the solution really is: You can't prevent it. Whenever you upgrade, the new version of ReadyAPI will do whatever it wants with regard to the empty XML fields... some versions will generate a beginning tag and end tag <tag></tag>, then the next version may decide to use the shortcut <tag/>, and the version after that may revert to the expanded <tag></tag> again, and there is nothing to be done but allow it. 😞

 

  • JoostDG's avatar
    JoostDG
    Frequent Contributor
    3 years ago

    Hi jrforeman .

    Have you tried the relatively new feature of "store locally" for the testSuite/testCase properties, that is available as of v.3.6. (see https://support.smartbear.com/readyapi/docs/testing/properties/local-properties.html) ?

    I can't say how it works with the empty fields over different versions, and obviously it's only for the <properties> tags, but it * might * help (no gurantee). 

     

    If you want to apply it to an existing project, here's a save script that can help set all these properties to "save locally" at once:

    https://community.smartbear.com/t5/ReadyAPI-Questions/How-to-set-quot-store-locally-quot-to-default-true-or-how-to-set/m-p/228223#M55322

    Disclaimer: Executing this script does mean you do not want any "hardcoded" testSuite/testCase properties directly in those properties menus. (You can still change/set them via e.g. a setup script).

    • jrforeman's avatar
      jrforeman
      Occasional Contributor
      3 years ago

      Hey JoostDG!

       

      Setting properties locally sounds like an useful feature.  Moving properties out of the project source would be a good way to avoid properties value changes that happen during each run, something I have done until now by using cleanup scripts. 

       

      The properties I'm talking about are mostly (all?) in properties test steps, which unfortunately don't offer any way to store locally.  Not sure it is worth the hassle to retrofit existing projects, though that script should help!  I will play with this local storage idea in new projects, and I may change my pattern for setting up test properties in the future to use property types that support storage in the user-local workspace.  Thanks for alerting me to the local storage option!

       

      JR