-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[#469] fix encryption ITs for changed MDA model
Part of the encryption IT scenarios were checking that the right number of fields were retrieved by the `get_field_list` method. I'm not sure that this makes sense as an encryption test. Either the encryption method (which uses `get_field_list`) encrypts fields correctly, or it doesn't. I don't see a ton of value in testing that method specifically over the actual encryption tests which indirectly test `get_field_list`. This changeset also splits off the vault scenarios into a separate feature, as those are the only real "IT" scenarios. We can't just tag the scenarios directly because the feature-level tag is used to determine whether we should stand up the Vault image, and we can't base this logic at the scenario level because that would tear down and deploy Vault between each scenario, which is wasteful since we aren't changing the state of Vault between scenarios.
- Loading branch information
1 parent
87e5f11
commit 86fd4bb
Showing
3 changed files
with
19 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
18 changes: 18 additions & 0 deletions
18
...ble-test-data-delivery-pyspark-model/tests/features/pyspark_data_encryption_vault.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
@pyspark_data_encryption @integration | ||
Feature: Data encryption | ||
|
||
Scenario: Specifying the Vault encryption algorithm yields a custom field encrypted with the corresponding algorithm | ||
Given a pipeline with native inbound collection and inbound record type | ||
When Vault encryption is requested | ||
Then the correct Vault algorithm is applied to the data set | ||
|
||
Scenario: Specifying the Vault encryption algorithm yields a dataframe field encrypted with the corresponding algorithm | ||
Given a pipeline with native non-collection inbound and no inbound record type | ||
When Vault encryption is requested | ||
Then the correct Vault algorithm is applied to the dataframe | ||
|
||
Scenario: Encrypt fields for native collection inbound without an inbound record type (set([DataFrame])) | ||
Given a pipeline with native collection inbound and no inbound record type | ||
When Vault encryption is requested | ||
Then the correct dataframe fields are vault encrypted for each dataframe | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters