17171 -- Wrong testbed when 'run' invoked via remote 'call'

The wrong testbed is used when a run step is invoked in a testcase that is executed via remote 'call' step and Testbed to use is set to be "Use testbed (if any) currently in use" in 'run' step property. For example,

testbed file for f1.fftc is tb1.fftb

testbed file for f2.fftc is tb2.fftb

testbed file for f3.fftc is tb3.fftb

f1.fftc has a 'call' step that points to f2.fftc (remote call)
f2.fftc has a 'run' step that points to f3.fftc with "Use testbed (if any) currently in use" setting for testbed to use under run property in the step properties of the run step

Execute f1.fftc. The testbed used for f3.fftc would be tb2.fftb.
This is incorrect, it should use tb1.fftb as that is the testbed of the f1.fftc.

Patch is available: iTest 3.4.1 Patch 41145 (KAZ-17171)

17171 -- Wrong testbed when 'run' invoked via remote 'call'

Labels