Im very interested in how you use markers and i guess you are already aware that you are in control of the marker?

I guess one can easily provide a custom maker which is just a uuid something like this ->

radish SomeFeature.feature -m uuid

In regulated environments, you have to be able to uniquely identify your testrun for documentation purposes. As far as I understood the documentation, this is the purpose of the marker. However, in my opinion, the current implementation does not serve this purpose very well, since there is a (small) chance that two different testruns produce the same marker, when started at the same time. A uuid would serve this purpose much better.

Yes, I am aware that I can control the marker from outside, so this is no big issue for me, but I was thinking this might be a good improvement for radish itself.

@realtimeprojects please take a look at the open MR if that is the thing you had in mind :)