juk

@happz thank for an update! Would you consider adding requirement group "device" as described in https://tmt.readthedocs.io/en/stable/spec/hardware.html#device ? In some cases like Driver Update Program we do not classify devices as...

> `device` should be one of the refactored and completed requirements, see https://github.com/teemtee/tmt/pull/2928/files#diff-1f37ee00a19e467a4f192fb6c06f6f3cce3b9e460896ed5397a89054bf58d085R1371 Oh sorry, missed it. Thank you!

Sorry, closed accidentally. Reopening

@pfdaly thank you for the commit! Do you have an example of results.yaml ? In the report output it's a bit hard to read sub-tests results because there is no...

> @juk, could you please review and test the proposed changes to ensure it covers your use case well? Thanks. @psss, I've tried the change with a few kernel tests...

> > @juk, could you please review and test the proposed changes to ensure it covers your use case well? Thanks. > > @psss, I've tried the change with a...

@pfdaly with the method proposed, we may be missing a few things in the results.yaml for a test plan. Not sure if it's intended to work this way, though. Would...

@psss I quickly checked a junit format and it seems like there is infrastructure to support subtests/phases classname - could be used for a parent test name name - could...

@idorax Right, create a .repo file Not sure if extra options like gpgcheck/gpgcheck are necessary We could have gpgcheck=0. Assuming user running tests know what they doing But I'll leave...

@lukaszachy, I understand your concerns. But at the end of the day it's a test environment that would be torn down after test. Not sure how often skip_if_unavailable=0 and gpgcheck=1...