Forum Discussion

nmrao's avatar
nmrao
Champion Level 3
9 years ago

Property, which is passed using -P to testrunner, is not available in afterLoadScript

Noticing the following behaviour while testing the options of testrunner (both SoapUI  NG / Open Source Edition).   Running a project using testrunner with -P<PropertyNamve>=<Value> option and re...
TanyaYatskovska's avatar
TanyaYatskovska
SmartBear Alumni (Retired)

Hi Rao,

 

Thanks for reporting this.

I've passed this behavior to our R&D Team. Could you please confirm that you see the same issue in Ready! API 1.6?

nmrao's avatar
nmrao
Champion Level 3
9 years ago

Thank you Tanya for taking it to R&D team.

Not checked on 1.6. However, as mentioned earlier, it appears that it is a latent defect(if this is accepted as defect by R&D), since it is not working SoapUI OS 4.x and Ready API 1.5, so I would expect that very few chances that it could work in 1.6 too.

  • JKambli's avatar
    JKambli
    Staff
    9 years ago

    Yes you are right the bug SOAP-3704 is not resolved as yet, but good news is team is working on this issue and should be fixed in upcoming release.

     

    Thanks

    • nmrao's avatar
      nmrao
      Champion Level 3
      9 years ago

      Thank you for letting know and glad to hear that.

       

      Hoping that it will be addressed in both the editons NG & OS

      • TanyaYatskovska's avatar
        TanyaYatskovska
        SmartBear Alumni (Retired)
        9 years ago

        Hi Rao,

         

        AfterLoadScript is being fired when loading a project with built-in project settings. The -P argument changes a property only after a project is loaded. I’ve consulted with our Dev Team and they suggest that you add your assertion to project’s Setup Script. The code located there will be executed before loading a project. Please let me know if this solution works for you.