Skip to content

test(sdk): DSPX-1561 run the shared assertion conformance vectors - #439

Draft
dmihalcik-virtru wants to merge 1 commit into
DSPX-1561-binding-verificationfrom
DSPX-1561-assertion-vectors
Draft

dmihalcik-virtru wants to merge 1 commit into
DSPX-1561-binding-verificationfrom
DSPX-1561-assertion-vectors

Conversation

@dmihalcik-virtru

@dmihalcik-virtru dmihalcik-virtru commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

Proposed Changes

  • Vendor xtest/vectors/assertions-phase0.json from opentdf/tests (the DSPX-5520 shared vectors) byte for byte as sdk/src/test/resources/assertion-vectors-phase0.json.
  • AssertionVectorsTest runs every vector: assertion hashing and Section 3 parsing, manifest-level parsing, binding forms, and Section 8 verification with a selected key. Required vectors must pass; proposed ones are logged. The assertion vectors also run through the manifest reader, spliced into a TDF. The test also checks that the SDK's modelled-names table equals the one in the file.
  • Test-only; no SDK changes.

Stacked on: #438. The vectors come from opentdf/tests#705, which should land first.
Split out of #432 (draft; the complete change). Cross-SDK counterparts: opentdf/platform#4308, opentdf/web-sdk#1142.

Checklist

  • I have added or updated unit tests
  • I have added or updated integration tests (if appropriate)
  • I have added or updated documentation

Testing Instructions

  • mvn -pl sdk -am test -Dtest=AssertionVectorsTest -Dsurefire.failIfNoSpecifiedTests=false, or the full mvn -pl sdk,cmdline -am test.

Vendor xtest/vectors/assertions-phase0.json from opentdf/tests (the
DSPX-5520 shared vectors) byte for byte, and run every vector: assertion
hashing and Section 3 parsing, manifest-level parsing, binding forms,
and Section 8 verification with a selected key. Required vectors must
pass; proposed ones are logged. The assertion vectors also run through
the manifest reader, spliced into a TDF.

Signed-off-by: Dave Mihalcik <dmihalcik@virtru.com>
@coderabbitai

coderabbitai Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

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