[geofencing-subscriptions] Deferred validation findings for r4.1 — G-004 scenario count

[jlurien]

Deferred validation findings — geofencing-subscriptions r4.1 / 0.6.0-rc.1

These findings appear in the CAMARA Validation output for PR #421 (Release Review r4.1).

---

G-004 — Too many scenarios in feature file (WARNING)

File: code/Test_definitions/geofencing-subscriptions.feature
[G-004] Number of scenarios exceeds maximum: 53/50

Deferral reason: The scenario count of 53 reflects the comprehensive test-plan alignment with CAMARA r4.3 testing artifacts merged in PR #414. Reducing the count would require removing valid test coverage. This will be addressed in a future revision by reorganizing the feature file (e.g. splitting into multiple files).

---

S-313 — String has no format/pattern/enum (HINT × 3)

File: code/API_definitions/geofencing-subscriptions.yaml
Lines: 579, 1035, 1067
[S-313] Schema of type string should specify a format, pattern, enum, or const.

Not applicable: These string properties are defined in CAMARA shared artifacts (CAMARA_event_common.yaml) and are referenced via $ref. They cannot be modified in this repository. No fix is required.

[hdamker]

@jlurien I have folded the G-004 issue into PR #439, which now splits the test definitions for the subscription API per operation. Which leaves only the one hint S-313 which does not need to be documented => PR #439 will fix the issue completely.