sample of TMT metadata for one test and one plan and how it could work. #283
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
This was referenced Dec 21, 2023
|
@jrusz I added you as a reviewer cause you're the latest committer to this repo 😇 I was wondering if this is supposed to be a draft, or closed or reviewed/updated/merged. |
I think this should be looked at by @narmaku .. I don't know if this is something they're interested in. But yeah feels like it should be a draft. |
|
Thanks @jrusz and @ochosi . This is an example of how our test suite could be used with tmt, made by @jscotka for us in CloudX team. We still need to evaluate the tooling itself so once we work on CLOUDX-857, we sill review this PR and play with it. |
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.
Example for @narmaku how TMT metadata could look like. Schedule via (schedule all plans)
be aware that
contextof environement is set by tooling liketmt --context distro=fedora-33 run(https://tmt.readthedocs.io/en/stable/spec/context.html) so adjusting test relevancy works when context is set by some tooling (testing farm CI set it automatically based on provisioned distro)