Kamil's suggestion was that rather than a result just providing a
single scenario value that's intended to be a not-very-human-readable
string that represents, in some sense, the entire 'scenario' for a
test, a result (let's say it's for the test update.base_selinux) would
provide something like this:
scenario_keys: [arch, machine, flavor, version, distri]
arch: x86_64
machine: uefi
flavor: server
version: 26
distri: fedora
Then if you're an rdb consumer and you wanted to be really sure you had
the entire 'description' of a given test you could represent it just by
displaying *all* those values, with or without the key name depending
on how it fit into your consumer's interface. But your consumer could
also think like this:
OK, I've got 50 results for this item. The arch, machine, version and
distri for *every* result are the same, so there's probably no need to
show those. But some of the results have different flavors. So I should
probably use 'testcase name - flavor' as the identifier, like so:
"update.base_selinux - server". Hey, that looks pretty good!