Container testing framework #298
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
cidrblock
added
enhancement
cidrblock
requested review from
ssbarnea,
Qalthos,
shatakshiiii,
NilashishC and
alisonlhart
and removed request for
a team
|
Tested locally - working! |
alisonlhart
approved these changes
Jul 10, 2024
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.
This PR lays the groundwork for container testing with pytest.
It has been implemented in such a manner the container tests will not currently run without specific pytest flags, this was done to avoid and impact to the current setup.
The container is started udring session start and stopped at session finish, with a fixture available to run commands in the container.
Container specific tests will be marked:
Usage example:
Only a single sample test is in place now.
Closes #276