sample of TMT metadata for one test and one plan and how it could work.

[jscotka]

Example for @narmaku how TMT metadata could look like. Schedule via (schedule all plans)

tmt -vv run

be aware that context of environement is set by tooling like tmt --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)

[ochosi]

@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.

[jrusz]

@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.

[narmaku]

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.