TP/NGSI-LD/DistributedOperations/Provision/EntityAttributes/AppendEntityAttributes/D003_01_exc.robot
+4
−2
Loading
Both tests appended attributes as application/json with NO Link header, so the
attribute names (e.g. speed) never expanded to the IRIs the exclusive
registration used. The exclusive match found nothing to forward, so the broker
made zero forwards where the tests expect one — D003_01_exc failed at the stub
count (0 != 1) and D003_02_exc timed out in Wait For Request. The broker is
correct: short names without a context cannot match the registration's
expanded IRIs.
Add an optional ${context} argument to the shared Append Entity Attributes and
Append Entity Attributes With Parameters keywords (emit the @context as a Link
header via Build Context Link; defaults to empty so the 17 existing callers are
unchanged), and pass context=${ngsild_test_suite_context} in both tests.
D003_01_exc also needed two latent fixes that only surfaced once the forward
worked: (a) the final check did Get From Dictionary ... speed on the local
view, which per § 4.3.6.3 correctly LACKS the exclusively-registered attribute
and raised before asserting — replaced with Should Not Contain on the entity
(as already done for D007_01_exc); (b) it used Retrieve Entity without
importing ContextInformationConsumption.resource where that keyword is defined.