Validating orderId, podId
ProductOrderData::orderId and ProductOrderData::podId are automatically computed if omitted.
The orderId is set to one of the service order.
The podId is set starting from 1 and incrementing for each pod.
Exact Matching, Implicit Scope
<test name="test_pod_orderId_1"> <flow>flow1</flow> <description>Test pod : orderId is computed if omitted (unscoped value)</description> <inject mod="getSo"> <so orderId="1"> <sod/> <pod/> </so> </inject> <expect mod="port1"> <so orderId="1"> <sod orderId="1"/> <pod orderId="1"/> </so> </expect> </test>
Exact Matching, Explicit Scope
<test name="test_pod_orderId_2"> <flow>flow1</flow> <description>Test pod : orderId is computed if omitted (scoped value)</description> <inject mod="getSo"> <so orderId="1"> <sod/> <pod/> </so> </inject> <expect mod="port1"> <so orderId="1"> <sod/> <pod orderId="test_pod_orderId_2@@1"/> </so> </expect> </test>
Regexp Matching
<test name="test_pod_orderId_3"> <flow>flow1</flow> <description>Test pod : no orderId specified, reOrderId used for validation</description> <inject mod="getSo"> <so orderId="1"> <sod/> <pod/> </so> </inject> <expect mod="port1"> <so orderId="1"> <sod/> <pod reOrderId="test.*"/> </so> </expect> </test>
Copyright © Cloud Software Group, Inc. All rights reserved.