After making the first steps with tmt and investigating the provisioning options let’s now dive together a little bit more and look Under The Hood to see how plans, tests and stories work together on a couple of examples.


Use Plans to enable testing and group relevant tests together. They describe how to discover tests for execution, how to provision the environment, how to prepare it for testing, how to execute tests, report results, and finally how to finish the test job.

    how: container
    image: fedora:33
    how: install
    package: wget
    how: tmt
    script: wget


Tests define attributes which are closely related to individual test cases. This includes the test script, framework, directory path where the test should be executed, maximum test duration , and packages required to run the test. Here’s an example of test metadata:

summary: Fetch an example web page
test: wget
require: wget
duration: 1m


Use Stories to track implementation, test and documentation coverage for individual features or requirements. Thanks to this, you can track everything in one place, including the project implementation progress.

    As a user I want to see more detailed information for
    particular command.
  - tmt test show -v
  - tmt test show -vvv
  - tmt test show --verbose

Core attributes

Core attributes cover general metadata. This includes: summary or description for describing the content; the enabled attribute for disabling and enabling tests, plans, and, stories; and the link key which tracks relations between objects.

    Different verbose levels can be enabled by using the
    option several times.
  - implemented-by: /tmt/
  - documented-by: /tmt/
  - verified-by: /tests/core/dry

Have a look at the whole chapter to learn more details and get some more context. See the Fedora Guide to learn even more about enabling tmt tests in the CI.