-
Notifications
You must be signed in to change notification settings - Fork 71
Test strategy for our providers on the CI #69
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
Comments
We could add an optional argument when launching Parsec to specify a configuration file path and use this one. That way we can have in-tree one configuration file per provider and test them independently 😄 And one more with all of them 😈 |
We would have the following test structure (in
The following
Exactly the same tests (except |
In order to execute the tests under different single providers, under all providers and for cross-compilation, split the tests directory into sub-directories. Each one contains a specific configuration file to run the tests under. Please check issue parallaxsecond#69 for details. Signed-off-by: Hugues de Valon <[email protected]>
In order to execute the tests under different single providers, under all providers and for cross-compilation, split the tests directory into sub-directories. Each one contains a specific configuration file to run the tests under. Please check issue parallaxsecond#69 for details. Signed-off-by: Hugues de Valon <[email protected]>
In order to execute the tests under different single providers, under all providers and for cross-compilation, split the tests directory into sub-directories. Each one contains a specific configuration file to run the tests under. Please check issue parallaxsecond#69 for details. Signed-off-by: Hugues de Valon <[email protected]>
I think it could be tested by changing nothing but having a different configuration file which points to the SoftHSM library. There is an available
Dockerfile
that installs the library that we can use.I think we also have to think how we are going to scale testing of multiple providers on the CI.
I was thinking of having single provider tests (our current tests) and multiple providers tests that test more the configuration as opposed to a provider implementation. For that purpose we should have multiple configuration files for all of those cases: one per provider and another one including them all.
The text was updated successfully, but these errors were encountered: