search

radish-bdd / radish

Behavior Driven Development tooling for Python. The root from red to green.
https://radish-bdd.github.io
MIT License
180 stars 49 forks source link

Consider using a uuid (uuid4) as marker #470

Open realtimeprojects opened 4 months ago

realtimeprojects commented 4 months ago

At this time the marker is derived from the epoch time. However, especially when running tests on different hosts in parallel, there is a chance that two seperate test runs might get the same marker. This violates the rules for certain regulatory requirements. Hence, we should use a uuid as a marker to eliminate this problem.

fliiiix commented 4 months ago

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
realtimeprojects commented 4 months ago

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.