Forum Discussion
rakuAnarchy
15 years agoNew Contributor
Using SoapUI 3.6.1
Similar behavior observed: testrunner.bat log (generated by Launch TestRunner) indicates everything ran successfully, including the explicit, Groovy scripted property transfer step, but the value was not transferred to the project or global level (transfers to both these levels is specified). The property transfer step works fine if the TestSuite is manually executed, but not from Launch TestRunner (from the shortcut menu) or from the command line. If the property transfer is already configured in a functioning test step, why are command line arguments, i.e., -G or -P necessary? Also, can command line arguments refer to response values? If so, what is the syntax? The example given refers only to a literal value (500).
I'd appreciate any help.
Similar behavior observed: testrunner.bat log (generated by Launch TestRunner) indicates everything ran successfully, including the explicit, Groovy scripted property transfer step, but the value was not transferred to the project or global level (transfers to both these levels is specified). The property transfer step works fine if the TestSuite is manually executed, but not from Launch TestRunner (from the shortcut menu) or from the command line. If the property transfer is already configured in a functioning test step, why are command line arguments, i.e., -G or -P necessary? Also, can command line arguments refer to response values? If so, what is the syntax? The example given refers only to a literal value (500).
I'd appreciate any help.