fix(020_17-020_20, 008_01): temporal setups without current-state pairing or duplicate timestamps (#95)

Ken Zangelinrequested to merge
fix/temporal-setup-regular-entity into develop
  • 020_17 / 020_18 / 020_19 / 020_20: the setup creates a regular entity (vehicle-different-attribute-types.jsonld, vehicle-with-scope.jsonld, new) instead of pairing a current-state POST into the temporal setup; the teardown deletes the entity and its temporal representation.
  • 020_19 / 020_20 expectations: a deleted scope is the NGSI-LD Null "urn:ngsi-ld:null" (TS 104-175 clause 4.18, 5.3.2.5), not [].
  • 008_01: the update re-sent instances at the timestamps the create had used. It now adds instances at new timestamps only, and the expectation is the union of both (append-only, TS 104-175 clause 5.6.11.4).

Tested - Against coraine: 0 / 9 on develop -> 9 / 9 (020_17 x3, 020_18 x3, 020_19, 020_20, 008_01).

🤖 Generated with Claude Code

Edited by Ken Zangelin

Merge request reports