doubts: #78 — DistOps write-op status-code mismatches (30 tests, 7 patterns, triaged)

Ken Zangelinrequested to merge
fix/distop-write-op-status-doubts into develop

Triage of the 30 DistOps tests whose HTTP status code comparison failed. Categorised into seven code-pair patterns with per-pattern diagnosis:

  • 8 tests (201≠409) confirmed as setup-design issues: the test creates a local entity and then a CSR (exclusive or redirect) for the same entity. Both modes correctly conflict with local data — the broker's CSR-creation-time conflict check fires (postCsourceRegistration.c ::conflictCheck, designed behaviour). Tests need original-author redesign. The 4 exclusive ones additionally need propertyNames in the CSR fixture (an exclusive CSR cannot claim a whole entity).

  • 5 tests (207↔️204 in both directions) are the open spec ambiguity already in spec-doubts-2 #90 (inclusive-mode forward-failure status). Defer until spec discussion lands.

  • 17 tests (204≠404, 200≠400, 201≠400, 200≠404 + 4 singletons) need per-test triage; structurally suggestive of the same setup-shape issues plus stub-URL gaps. No firm conclusion without inspection.

For all 30, the broker is at minimum spec-defensible — no broker-side change is recommended. Documenting the analysis so the team can pick up specific tests with context, rather than re-triaging from scratch.

Merge request reports