add "custom server" macro for tests #30
Merged
Conversation
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
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.
Adds macro to protect portions of the crypto tests that require custom logic on the server side, that would prohibit them from being run against a standard server.
This is required for
whTest_CryptoClientConfig()to run against a standard server on the HSM core on real hardware.This is not a long-term solution on its own - instead we should separate tests into single client and multi-client tests in addition to those requiring custom servers, as well as standardize a demo routine separate from the unit tests.
Apologies for the double-negative macro, but I wanted to keep this off by default to avoid breaking things and touch as little code as possible (since this is a temporary solution)