I agree that it's useful when the test step starts at the same time as the test step defined in Start Step property - sometimes.
It's also useful when the test step starts after the test step before - especially when I want to test the sequence of messages. This can not be done when the sequence of messages is not quite clear defined - as it is when I define a start step sequentially in several test cases.
My example shows several mock responses after each other. Each test step defines the previous one as Start Step:
- Groovy script
- Mock response 1 with Start Step Groovy script
- Mock response 2 with Start Step Mock response 1
- Mock repsonse 3 with Start Step Mock response 2
If the test step in question starts at the same time as the test step defined in the Start Step property does that mean that all test steps start parallelly?
In my example it would mean that Mock response 1, Mock response 2 and Mock response 3 would start at the same time as Groov script.
I suggest that the user can define when the test step should start - at the begin or at the end of the test step defined in Start Step property.
