Loading
fix(047): align the csub-notification tests with TS 104-175 clause 12.4.7
Clause 12.4.7: the initial csource notification is sent UNCONDITIONALLY
on subscription (with an empty data array when no CSR matches), and
periodic (timeInterval) notifications fire regardless of changes. The
047 family assumed no notification arrives when nothing matches:
- every setup that creates the subscription before (or without) a
matching CSR now consumes the initial notification, so later waits
see the intended one (047_03/04/05/07/08/09/10..16)
- 047_02/04/08/09 paired the Building-watching subscription with the
Vehicle+OffStreetParking CSR — per 12.4.7 these do NOT match; they
now use the Building-and-Bus CSR (as 047_03 already did). The
endpoint-update (still matching → "updated") and
information-replacing ("noLongerMatching") fragments work unchanged
- 047_05 verifies the success bookkeeping on the initial notification
itself; the non-matching CSR creation must then trigger nothing
- 047_06's expectation gains timesFailed (clause 12.4.7 failure
bookkeeping)
- Update CSR Subscription keyword: optional context arg → Link header;
047_16's selector patch needs the test-suite @context or 'Vehicle'
expands against the default context and matches nothing
- NotificationUtils validator: entityInfo type can be a string or an
array — indexing [0] into a string yields its first character
('Building' != 'B')