Contributions
Re: Creating properties at the Test Case level, initialized by Groovy scripts
Thanks much. Yes; that's what I tried to do. I reviewed what you earlier wrote in other posts, and cleaned up the code, trying again to set those values the way you note below. When I try to import (Get Value) those time strings (xsd:dateTime (there's three)) to the request, the editor would revert them to ${CurTime}, an earlier entry. I used the Set Value option to put that string into the SOAP request. It appears that the "${#TestCase#CurTime}" is what is being sent, and not the data. I see a similar issue with {#TestCase#messageID}; If I place a known string at the Test Case property level, the test step gets it. If I try to set that property from the Groovy Setup Script, it's not seen.1.7KViews0likes0CommentsCreating properties at the Test Case level, initialized by Groovy scripts
Hi - Have been trying to set properties at the Test Case level, initialized by Groovy Setup scripts at that Test Case level, accessible by the Test Steps beneath that Test Case. The properties are wrote and read and logged during the Setup script execution, but don't show in the sent Soap request. It appears that CurTime is null with the request. CurTime is referenced in the xml below - the three time values The Setup Script excerpt: testRunner.testCase.setPropertyValue("CurTime", CurTime); log.info "time is "+CurTime; log.info "Start time is: " + testRunner.testCase.getPropertyValue("CurTime"); --- ${#TestCase#messageId} L243 ? --- The property CurTime is also listed at the Test Step Properties level, and has an initial value of ${CurTime}. This is under SoapUI-Pro 2.0.24.4KViews0likes8Comments