Forum Discussion
Kathryn_O_Malle
16 years agoContributor
Hi,
Thanks for that. In isolation I can get the code to work but when I insert it into my project I can write to the list variable but I can't read from it; instead I get "null". I think I'm hitting scope issues with my setup.
I create and write to the list variable in testsuite1. Inside testsuite1, a script calls testsuite2. When I try to read the list variable in testsuite2 I get nothing. I suspect the list variable has gone out of scope at this point.
As per http://www.soapui.org/Scripting-Properties/working-with-properties.html is there a way to modify the code so as to specfiy a #global# or #project# scope for this variable. Due to our current setup, defining the list variable in the project startup script would hinder our debugging process at times.
Many thanks.
Thanks for that. In isolation I can get the code to work but when I insert it into my project I can write to the list variable but I can't read from it; instead I get "null". I think I'm hitting scope issues with my setup.
I create and write to the list variable in testsuite1. Inside testsuite1, a script calls testsuite2. When I try to read the list variable in testsuite2 I get nothing. I suspect the list variable has gone out of scope at this point.
As per http://www.soapui.org/Scripting-Properties/working-with-properties.html is there a way to modify the code so as to specfiy a #global# or #project# scope for this variable. Due to our current setup, defining the list variable in the project startup script would hinder our debugging process at times.
Many thanks.