load_key tests: Re-route to the parsec provider #27
Conversation
This file contains hidden or 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
The load_key test is being routed to the default provider so as to test that the test itself is correct. Now that this is confirmed: * Make the load_key test route the calls to the parsec provider instead. This will now verify that the key management functions are implemented correctly. * Remove todos * Modify the ci.sh script to print required logs when running tests. The following changes will temporarily break the CI but are necessary to test the keymanagement implementation. Signed-off-by: Tomás González <tomasagustin.gonzalezorlando@arm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The load_key test is being routed to the default provider so as to test that the test itself is correct.
Now that this is confirmed:
The following changes will temporarily break the CI but are necessary to test the keymanagement implementation.