Skip to content

Parameterize the negative signature tests across all ML-DSA parameter sets - #2

Merged
ffang merged 1 commit into
ffang:PQC-SIGNATUREfrom
Arpan0995:pqc-signature-negative-tests
Aug 21, 2026
Merged

Parameterize the negative signature tests across all ML-DSA parameter sets#2
ffang merged 1 commit into
ffang:PQC-SIGNATUREfrom
Arpan0995:pqc-signature-negative-tests

Conversation

@Arpan0995

Copy link
Copy Markdown

As discussed on apache#645: this converts the tampered-SignatureValue and wrong-public-key tests on both the DOM/JSR-105 and StAX paths to @ParameterizedTest/@CsvSource across ML-DSA-44/65/87, in the same style as the existing sign-and-verify tests. The StAX helper now takes the signature and key algorithms as parameters instead of hardcoding ML-DSA-65. The happy-path tests are untouched.

Verified locally on this branch:

  • mvn test -Dtest=XMLSignatureMLDSATest,StaxMLDSASignatureTest -P bouncycastle: 9 + 9 executions, 0 failures
  • same command without the bouncycastle profile: compiles and all 18 executions skip via the existing assumeTrue guards

… sets

Converts the tampered-SignatureValue and wrong-public-key rejection
tests on both the DOM/JSR-105 and StAX paths from single hardcoded
ML-DSA-65 cases to @ParameterizedTest/@CsvSource across ML-DSA-44/65/87,
matching the style of the existing sign-and-verify tests. The StAX
helper takes the signature and key algorithms as parameters instead of
hardcoding ML-DSA-65.
@ffang

ffang commented Aug 21, 2026

Copy link
Copy Markdown
Owner

Thanks @Arpan0995 !

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.

2 participants