I have a folder within a collection. I am using Collection Runner to run the queries within this folder. The second query uses data returned from the first. Therefore if the first query fails any of the tests in its test script, I need the run to stop immediately.
In practice this is not happening - the first query fails but the second still automatically runs.
Searching for this issue I found people making the opposite complaint - their queries were not dependent upon each other and therefore they wanted the run to keep going even if a query failed, but they were observing the behaviour that I want.
I can understand the Collection Runner having been enhanced with a new feature to allow it to continue upon the failure of a query in a collection, but as a rule, new features in products are added as options - they do not change default behaviour (because that, in general, will cause existing deployments that rely on the default behaviour to break).
So I am confused.
Does anyone have any insight into the behaviour that I am observing?