#21 Define how a testset is identified
Closed 3 years ago by psss. Opened 4 years ago by psss.

It should be possible to host both L1 and L2 metadata in the same repository. We need to define a clear way how identify testset among other nodes in the fmf.Tree. We have already discussed (but I don't see it anywhere documented) that the test attribute should be mandatory for each test. Then you can do:

fmf show --key test

Brainstorming: Perhaps we could require, that a valid testset needs to have at least the execute step defined. Then we could similarly do:

fmf show --key execute

What do you think? Any other suggestions how we could distinguish L1 and L2 metadata in a single metadata tree?


Metadata Update from @psss:
- Issue tagged with: L1 Metadata, L2 Metadata

4 years ago

Yes, I believe execute key should be mandatory ... thus I think this makes sense ...

+1. As discussed on IRC, we will need some sort of "reserved words" list, to disallow presence of test in testsets and execute in tests.

Metadata Update from @psss:
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata