Include an example template for creating tmt tests
#2754
Conversation
psss
requested review from
lukaszachy,
happz,
thrix and
janhavlin
as code owners
|
Related to the discussion in #2744. |
Vast majority of tests verifying the `tmt` features shares a similar outline of the `beakerlib` skeleton. Let's make it super easy to start writing a new `tmt` test. The skeleton also covers submitting `log.txt` when something goes wrong during the test execution so that a detailed investigation is possible later.
|
This is about how to expand PS: with beakerlib+homebrew, we might want to rethink how to source |
Could you explain a bit? |
There was a problem hiding this comment.
framework: beakerlib is missing
| ================================================================== | ||
|
|
||
| When creating a new ``tmt`` test it is recommended to use the test | ||
| template provided in this directory. In order to be able to use it |
There was a problem hiding this comment.
How about a link to https://tmt.readthedocs.io/en/stable/guide.html#custom-templates ?
Otherwise it is confusing why files are linked as .j2 to some directory which might not yet exist.
The issue is about: source /usr/share/beakerlib/beakerlib.shThis can't be the install path for beakerlib on homebrew also because on macos and linuxbrew they are different. It needs to be editable, most likely through |
| ln -sr test.sh ~/.config/tmt/templates/script/tmt.j2 | ||
| ln -sr main.fmf ~/.config/tmt/templates/test/tmt.j2 |
There was a problem hiding this comment.
This is using the user-configuration (thought it was still a draft), but for these templates it would make more sense to be on the project level since each project might have slightly different beakerlib scripts. That doesn't seem to be in the spec/stories, and I'm not sure where a project's template files would reside. The only place I can think of would be path/to/fmf_root/.fmf/templates/
Vast majority of tests verifying the
tmtfeatures shares a similar outline of thebeakerlibskeleton. Let's make it super easy to start writing a newtmttest. The skeleton also covers submittinglog.txtwhen something goes wrong during the test execution so that a detailed investigation is possible later.Pull Request Checklist