Loading
TP: tag 37 tests as swbroker_known_bad — implementer-side filter
These tests document known fixture / spec-arguable issues from the
testsuite-doubts log in swNgsild/doc/testsuite-doubts.md. The tag lets
the implementer use --skip swbroker_known_bad when running the suite
against a broker that takes the stricter spec reading.
Categories (see testsuite-doubts.md):
- §16/17 missing ResourceNotFound resource imports (4)
- §18 wants 503, spec says 504 (2)
- §19 Robot URL stripping mangles implicit URL (1)
- §20 fixture core_context v1.6 vs broker's v1.9 core (3)
- §21 Content-Type ld+json + Link header (1) — forbidden per §6.3.5
- §23 Robot "1 (integer) != 1 (string)" strict compare (8)
- §24 missing keyword 'Get Request Url Params' in HttpCtrl (3)
- §25 fixtures expect un-filtered RegistrationInfo set (2)
- §26 037_10_01 three layered fixture bugs (1)
- §27 pagination offset confusion (2)
- §28 ?id= alone per §5.7.2.4 too wide (4)
- §29 ?page= non-standard pagination (3)
- Robot keyword bugs (3): D010_01_aux, D011_01_aux, D009_01_inc
37 .robot files touched; existing passing 037_09_01..04 explicitly
excluded from the tag (they pass in suite context).
Co-Authored-By:
Claude Opus 4.7 (1M context) <noreply@anthropic.com>