Is there a way to stagger execution starts in the cloud runs.
When doing cloud runs is there a way to stagger the start of each test in the execution set so they don't all start at once.
Some of our tests have similar startup processes. The data is identified by the date and time. If the data is created in separate seconds everything works fine, but occasionally, data is created in the same second and things get confused. There are other options around this, but a staggered start time would help.
This just occasionally happens. It is probably mostly an issue I have with two separate execution sets.
That is why I phrased it the way I did. The two solutions I could think of are to have each test case in an execution set start 5 – 10 seconds after the previous, or add some sort of random wait time to the start of each test case to allow for a test start delay. I am not necessarily looking for a Subject7 change. I just wanted to see if something was available which I couldn’t find. Although a staggered/delayed start would be useful, I can work around it.
William
Please sign in to leave a comment.