ValueTransfers are TestCase steps that transfer values from a message response to
the following request message. They hold an arbitrary number of "value transfers", each containing a
source and destination xpath expressions.
ValueTransfers use the same Saxon XPath engine as described for the XPath Assertion. |
![]() |
Upon execution during a TestCase run, each transfer in the ValueTransfer is performed by selecting the node specified by the transfers source xpath expression from the preceding response message and copying that value to the destination xpath applied to the subsequent TestRequests request message.
The source and target xpath expressions must both point to existing nodes in their respective messages, the response message obviously requires the node so it can be selected, the request message requires the node so it can be found and overwritten with the value copied from the preceding request message.
The nodes selected by the source/target expressions must be assignable; they must either be of the same type (ie both are elements, attributes, etc) or of different types that could be assignable (ie a text() source to a @attribute destination). The transfer implementation will do its best to copy nodes of different types.
If any of the transfers fail due to missing matches of any of the xpath expresion, an error is printed and that transfer is ignored. The TestCase run is not aborted.
The ValueTransfer editor is opened by double-clicking a ValueTransfer test step either in the navigator or in the TestCase editors test-step-list.
The editor contains a list of configured transfers to the left, selecting a transfer in the list will displays that transfers source and destination xpath expressions to the right.
The following actions are available from the bottom toolbar
A ValueTransfer can be created as follows:
//ns1:SessionId
which will result in the sessionId element being copied
from the preceding response to the following request (where it must be available but preferrably empty)