@mvadkert, @pvalena, please review.

It's not that much apparent what --all does, and one might think it runs "all tests".

If I run on github, my package might not be installed (or will it be? packit integration should be linked here).

Do I need -f (force) here to view the report? Also might me worth mentioning --last links to last run per-user, not per-project (or am I wrong?).

Maybe mention this is an example git repository with test metadata?

this is installing tmt from copr repository right? additional installation options sounds a bit weird to me

fedpkg might need installing, it is not pulled in with any deps

also if somebody would be testing without a fedora account, they might need

fedpkg clone -a bash

is a bit misleading, maybe use standard

$ tmt init --template mini
....

yep it is needed

it will be installed, testing farm there installs the whole copr build

I would just mention "Fedora CI support", we are not targeting testing of dist-git PR for the start

Not necessarily. It makes sense to me. It's packaged in Fedora, so I expect users to want the stable bits, which means they expect to run test suite in packaging (%check), install checks etc.. Not everyone wants the 'latest greatest'.

Yes, but at the same time, our audience would be packagers, so this is fine.

~~Right, but testing farm is nowhere mentioned in this guide. Link it maybe?~~ EDIT: it is, great!

Well IMO Fedora users wan't explanations, because they want to understand what is being done and why. Some maybe include the descriptions of the args when it's used (and when it's needed as well).

Looks great!

Thanks for the comments. Content updated.