Test both runtimes in unit tests #1155
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
nitzmahone
approved these changes
Nov 4, 2022
Shrews
added a commit
to Shrews/ansible-runner
that referenced
this pull request
Nov 4, 2022
(cherry picked from commit 79b564d)
Shrews
added a commit
to Shrews/ansible-runner
that referenced
this pull request
Nov 4, 2022
(cherry picked from commit 79b564d)
Shrews
added a commit
that referenced
this pull request
Nov 4, 2022
Shrews
added a commit
that referenced
this pull request
Nov 4, 2022
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.
Unit tests do not need a runtime (docker or podman) actually installed to test code paths that depend on the runtime. The
@pytest.mark.test_all_runtimesfixture checks for installed runtimes. Change this to just parametrize the runtime name.Fixes #1153