Skip to content

test: support expected generation and byte-operation errors - #451

Open
harrshita123 wants to merge 1 commit into
google:masterfrom
harrshita123:fix/issue-55-operation-errors
Open

harrshita123 wants to merge 1 commit into
google:masterfrom
harrshita123:fix/issue-55-operation-errors

Conversation

@harrshita123

Copy link
Copy Markdown
Contributor

Summary

  • Allow test vectors to name a key-generation or byte-operation failure and assert its error type and message.
  • Validate the inputs for the selected operation so unrelated data is not silently ignored.
  • Add AES-GCM vectors for invalid key length and tag length, plus focused runner coverage for signing, verification, encryption, decryption, and key derivation.

This is a follow-up to #55. PR #450 covers the issue's key-import example; this change extends the runner to generation and byte operations. It does not add stream-operation or key-export error vectors.

Testing

  • dart test --exclude-tags browser-interop,sanitizer -p vm,chrome -c dart2js,dart2wasm -r compact — 4,701 passed, 1 skipped.
  • Focused operation-error and AES-GCM vector tests passed on VM, Chrome Dart2Js, and Chrome Dart2Wasm.
  • dart analyze --fatal-warnings . — passed.
  • git diff --check upstream/master...HEAD — passed.

This branch has not been deployed

No deployments
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