Loading
fix: csub status checks broken by the mandatory initial notification (clause 12.4.7)
Per TS 104-175 clause 12.4.7 an initial notification is sent unconditionally upon csource subscription creation. The csub fixtures point at an unreachable endpoint (http://localhost:1111/notify), so a compliant broker may legitimately report status 'failed' (and live counters inside 'notification') right after create: - 038_03 / 038_06: the status assertion now accepts 'active' or 'failed' (the tests' intent — not 'paused' / not 'expired' — is preserved). New keyword 'Check Response Body Containing an Attribute set to one of'. - 038_01 / 040_01: ignore the broker-computed Additional Members of NotificationParams (clause 5.2.14.2) nested under 'notification', as the entity-subscription twins (028_01, 030_03) already do. - assertionUtils.py: pass threshold_to_diff_deeper=0 to DeepDiff. Since deepdiff 8, when more than 1/3 of a dict's keys differ the whole dict is reported as changed instead of descending, silently bypassing exclude_regex_paths that target the nested keys.