We've decided to stop generating execution IDs client side. However, that wasn't the only place the ruby test collector was using SecureRandom.uuid, so am also still including the patch that @ChrisBr submitted that @blaknite then added to
Has been integration test against bk/bk
There'll be a follow up PR on bk/bk that also ignores any execution IDs that are sent from test collector clients but this PR can be merged and released independently of that
Builds upon #189 and #187
We've decided to stop generating execution IDs client side. However, that wasn't the only place the ruby test collector was using SecureRandom.uuid, so am also still including the patch that @ChrisBr submitted that @blaknite then added to
Has been integration test against bk/bk
There'll be a follow up PR on bk/bk that also ignores any execution IDs that are sent from test collector clients but this PR can be merged and released independently of that