Successfully decrypting your own output is not sufficient verification. Known valid and invalid vectors reveal implementation defects.
Evaluation approach
Use established vectors for the supported algorithm and API. Include boundary cases and verification failures.
Application example
Changing one byte of a signed message should fail validation, and the application must not process it anyway.
Limits and considerations
Passing vectors does not validate the entire protocol or key lifecycle.
Why include invalid examples?
Bad signatures, altered data and invalid parameters need safe rejection. Two components sharing the same mistake can pass a round-trip test while both remain wrong.
Checks and decisions
- Include negative cases
- Record API versions
- Check failure outcomes
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.