Tooling for running collection tests locally ad hoc #14160
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
github-actions
bot
added
the
component:awx_collection
gamuniz
reviewed
Jun 22, 2023
AlanCoding
force-pushed
the
fast_integration
branch
from
7c2982c
to
ac49eac
Compare
gamuniz
approved these changes
Jun 22, 2023
jessicamack
approved these changes
Jun 22, 2023
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.
SUMMARY
I have maintained a silly gist with instructions for running the collection integration tests here
https://gist.github.com/AlanCoding/2adb1590489912233117aa572b44b85a
This PR is attempting to fully finalize that to hand over to other developers to run generally.
I would like to eventually run in CI as a part of the dev environment check (because only that check actually has a server running). That requires running all the integration tests, but if we do that, I believe we should cut out some slow actions.
This is stripped down a little bit from what I had before, because I really don't want people to run all the tests. This should be focused on the case of running just 1 test module, and you should wrap that in bash for loops or whatever you want to do more.
ISSUE TYPE
COMPONENT NAME