Skip to content

Unit tests: Add a parsec_provider_init test with pre-generated parsec keys #30

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 2 commits into from
Apr 4, 2024

Conversation

tgonzalezorlandoarm
Copy link
Member

Use parsec-tool to generate a key out of bands

Add a parsec_provider_init test

The test checks if pre-generated keys can be accessed through the parsec client after initializing the provider.

This guarantees that:

 1) The parsec_provider_init function correctly initializes the
    parsec client.
 2) The parsec_provider_init function returns the correct pointer
    with the provider context.
 3) The parsec client is reachable through the provider context
    and is able to contact the parsec service.
 4) The pre-generated keys have been correctly stored through the
    parsec-tool

@tgonzalezorlandoarm
Copy link
Member Author

Please check
https://github.com/parallaxsecond/parsec-openssl-provider/actions/runs/8540977558

for the CI run with the newly built docker image

This key will be used by the provider when testing for key
management and signing operations.

Signed-off-by: Tomás González <tomasagustin.gonzalezorlando@arm.com>
@tgonzalezorlandoarm tgonzalezorlandoarm force-pushed the tg/test-w-parsec-tool-key branch from 95dad71 to 1c67443 Compare April 3, 2024 16:06
@tgonzalezorlandoarm
Copy link
Member Author

@tgonzalezorlandoarm tgonzalezorlandoarm force-pushed the tg/test-w-parsec-tool-key branch from 1c67443 to 15dd993 Compare April 4, 2024 09:24
The test checks if pre-generated keys can be accessed through the
parsec client after initializing the provider.

This guarantees that:

 1) The parsec_provider_init function correctly initializes the
    parsec client.
 2) The parsec_provider_init function returns the correct pointer
    with the provider context.
 3) The parsec client is reachable through the provider context
    and is able to contact the parsec service.
 4) The pre-generated keys have been correctly stored through the
    parsec-tool.

Signed-off-by: Tomás González <tomasagustin.gonzalezorlando@arm.com>
@tgonzalezorlandoarm tgonzalezorlandoarm force-pushed the tg/test-w-parsec-tool-key branch from 15dd993 to 9cb41c8 Compare April 4, 2024 09:35
@tgonzalezorlandoarm
Copy link
Member Author

Copy link
Collaborator

@gowthamsk-arm gowthamsk-arm left a comment

Choose a reason for hiding this comment

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

LGTM :)

@tgonzalezorlandoarm tgonzalezorlandoarm merged commit 5d0bafb into main Apr 4, 2024
@tgonzalezorlandoarm tgonzalezorlandoarm deleted the tg/test-w-parsec-tool-key branch April 11, 2024 09:13
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