You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Putting our tests in a structure that matches the source code helps a lot in making the tests discoverable and simple to map to the source that they are testing. We should restructure the tests in this repo to match the source structure, similar to how we structured tests in https://github.com/aws/aws-dynamodb-encryption-python.
The text was updated successfully, but these errors were encountered:
* reorganize keyring tests to match #100 and keyring namespace to simplify names
* change aws_encryption_sdk.keyring to aws_encryption_sdk.keyrings for consistency in namespace names
* autoformat
* disable pylint similarity checks on imports
Because we provide multiple implementations of certain types of things (keyrings, etc),
this was triggering pylint due to them all needing to import the same types in order to function.
* remove aws_encryption_sdk namespace layer in test reorg
* reorganize keyring tests to match #100 and keyring namespace to simplify names
* change aws_encryption_sdk.keyring to aws_encryption_sdk.keyrings for consistency in namespace names
* autoformat
* disable pylint similarity checks on imports
Because we provide multiple implementations of certain types of things (keyrings, etc),
this was triggering pylint due to them all needing to import the same types in order to function.
* reorganize functional and integration tests
* define structure for unit tests reorg
* reorganize unit tests
* rename test_values to vectors to avoid it being confused for a test file
* remove aws_encryption_sdk from functional test namespace
* remove aws_encryption_sdk from integration test namespace
* remove aws_encryption_sdk from unit test namespace
* rename test_crypto to vectors to avoid confusion
* autoformat
Putting our tests in a structure that matches the source code helps a lot in making the tests discoverable and simple to map to the source that they are testing. We should restructure the tests in this repo to match the source structure, similar to how we structured tests in https://github.com/aws/aws-dynamodb-encryption-python.
The text was updated successfully, but these errors were encountered: