Skip to content
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

IMP exec test framework #47

Open
grondo opened this issue Feb 6, 2018 · 1 comment
Open

IMP exec test framework #47

grondo opened this issue Feb 6, 2018 · 1 comment
Assignees

Comments

@grondo
Copy link
Contributor

grondo commented Feb 6, 2018

A strategy or framework is required for testing of the flux-imp exec subcommand. The test framework should allow the functionality of the exec command to be at least partially tested in simulated environments, e.g. run under fake or manufactured resource hierarchy ensure the IMP works when it should and fails properly when the resource configuration should not allow 3rd party execution.

Ideally the test framework could be fed a set of simulated environments and IMP inputs and ensure the results matches the set of desired outcomes for ease of test development.

@grondo grondo added this to the IMP-exec-subcommand milestone Feb 6, 2018
@grondo
Copy link
Contributor Author

grondo commented Feb 6, 2018

It occurs to me that there is a clear testing delineation between tests for the base flux-imp exec functionality and tests for the containment and other IMP plugins that are part of exec and which may require privilege. We'd have to think through this, but I think the former probably does not require privilege, and tests of the core exec functionality could be driven from make check without sudo, perhaps using a set of testing containment plugins built just for this purpose.

Tests for the real containment and other privilege plugins will perhaps require a different scope and different framework (one that will require privileged operation), though it will still be very important to have a good strategy for standalone testing here, as that will be invaluable for plugin developers to test their implementations to at least some extent outside of a real flux environment. More thought needed here.

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

No branches or pull requests

1 participant