response doesn't work in CallProcedure

Question

question

dclaar Suspended asked Feb 28, '11 dclaar Suspended posted Feb 28, '11

response doesn't work in CallProcedure

iTest 4.1.0

If I do CallProcedure with [response .], noting is passed to the procedure. If I set var [response .] and then CallProcedure with $var, the response is passed.

main

Step	Action	Session	Description
1	eval		puts "This is a test"
analyze
none
assert		"true"
When True		Details
CallProcedure		return_to_sender [response .]
When False		Details
2	eval		puts "This is a test"
analyze
none
assert		"true"
When True		Details
Eval		set resp [response .]
CallProcedure		return_to_sender $resp
When False		Details

return_to_sender

Step	Action	Session	Description
1	eval		puts ${arg[1]}
analyze
none
assert		"true"
When True		Details
DeclareExecutionIssue		OK:The answer is: [response .]
PassTestIfNotAlreadyFailed
When False		Details

Execution Issues

Index	Severity	Originator	Message	Location
	info	execution	Execution started
1.1.1	pass	analysis	The answer is:	/procedures/1/steps/0
2.1.1	pass	analysis	The answer is: This is a test	/procedures/1/steps/0
2.1.1	pass	execution	Test case return_to_sender has passed.	/procedures/1/steps/0
	info	execution	Execution completed (0s)

iTest bug

return_to_sender.fftc.html (7.3 KiB)

return_to_sender_2011-02-28_13-59-04.html (17.7 KiB)

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2011-10-17T19:44:33Z

EricGregMiller answered Oct 17, '11 EricGregMiller posted Oct 17, '11

This looks like it's kind of the opposite of the problem discussed at Problems with lists and passing them to Procedures. It is my understanding that iTest doesn't provide command expansion in procedure calls.

If this is a problem for you, keep this thread going and I can investigate further.

1

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

JeffJ ♦ commented · Oct 17, 2011 at 07:56 PM

The situation here is that the CallProcedure is a delayed action in the analysis rule. That means that the call is not executed until the step/analysis is finished. There are many reasons for this so I'll not expand on that at this time. Since the "callProcedure" is not executed until after the step is complete, the resolution of [response .] is null as there is no response to provide.

However, you can accomplish what you are seeking in a couple of ways.

First, use an "eval" action just before the "callProcedure" action to save the response in a variable. Then pass the variable to the "callProcedure" action.

The other method is to store the entire response in a variable via "Step Properties->Other Post-processing->Store Response", then use the [response <variablename>]" to send the response to the "callProcedure".

If you need help in setting this up, I can provide an example of either method.

0 ·

question