Forum Discussion
Ed_Bosco
16 years agoNew Contributor
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.
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.
Related Content
- 3 years agoCata