Skip to content

docs: add contract fixture comparison and redelivery checks - #16

Draft
upgundecha wants to merge 1 commit into
mainfrom
docs/contract-fixtures-redelivery
Draft

upgundecha wants to merge 1 commit into
mainfrom
docs/contract-fixtures-redelivery

Conversation

@upgundecha

Copy link
Copy Markdown
Owner

Change

Extend the selection guide with evidence for running the same versioned contract fixtures against an emulator and its real service. Record separate run dates/results, fixture revision, emulator and client versions, relevant cloud configuration, and known differences or unrun cases in the evaluation checklist and decision record.

Add an object → queue → worker evaluation scenario in which processing commits a side effect before acknowledgement fails, followed by redelivery and verification of duplicate handling. Distinguish failed settlement from a successful settlement whose response is lost. Update the adoption sequence to include this scenario where the service and receive mode support it.

Evidence and usefulness

The guidance helps readers distinguish application duplicate handling demonstrated locally from service delivery semantics requiring cloud validation. It describes an evaluation approach, without adding unverified executable examples or claiming that the catalog runs compatibility tests. No tool entries or license classifications change; no vendor affiliation is asserted by this change.

Validation: npm ci --ignore-scripts and npm run lint passed on Node.js 24. The changed selection guide also parsed as GitHub-flavored Markdown, with consistent columns in all 14 tables. No emulator or real-cloud integration tests were run; this PR adds documentation only.

Checklist

  • I read CONTRIBUTING.md.
  • The guidance is in scope and not duplicated; no new tool entry is added.
  • I checked upstream documentation; tool maintenance review is not applicable to this guidance-only change.
  • Formatting is correct; alphabetical tool ordering is unchanged.
  • Emulation, application fault injection, and real-cloud validation are distinguished accurately.
  • I ran npm run lint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant