Skip to content

feat: Encryption tests for integration-node #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 21, 2019

Conversation

seebees
Copy link
Contributor

@seebees seebees commented Jul 18, 2019

https://github.com/awslabs/aws-crypto-tools-test-vector-framework defines an encryption manifest.
This manifest should be used to maintain cross compatibility of language implementations.

Then integrate this into the CI integration tests.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

https://github.com/awslabs/aws-crypto-tools-test-vector-framework defines an encryption manifest.
This manifest should be used to maintain cross compatibility of language implementations.

Then integrate this into the CI integration tests.
@seebees seebees requested a review from a team July 18, 2019 22:46
if (result) {
console.log({ name, result })
} else {
if (err && notSupportedDecryptMessages.includes(err.message)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to enumerate the vectors that are not supported? Right now, if something returns not supported, but should be, it would slip by. That being said, this can go into a new issue, and doesn't need to be fixed here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or is that what "tolerateFailures" does?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tolerateFailures is just a count of failures to tolerate. CI should be 0.

Your comment is true. The hope is to come up with a results manifest. That could be compared and determine success.

@seebees seebees merged commit d7b5e73 into aws:master Jul 21, 2019
@seebees seebees deleted the decrypt-oracle branch July 21, 2019 15:04
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