@jscotka has experimented with storing fmf metadata using decorators directly in the Python code:
It could be useful to add support for such parsing directly to fmf. By default, *.fmf files would be checked only, a dedicated option could be used to enabled parsing *.py files as well.
Metadata could be combined from both sources:
fmf --extension fmf --extension py
In tmt the discover step could support a relevant option to enable such behaviour:
discover:
how: fmf
extension: [fmf, py]
Just the first brainstorm of possible syntax...