You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to propose an externsion to the testing feature.
Since the spec .yml file essentially maps to a linear chain of calls, it would be useful sometimes to alter the execution order of those queries.
For example, if some call fails an assertion there might not make much sense to run the rest of the call chain. This could be signalled somehow in the tests section.
Another case when further execution may better be stopped is when there's been a problem with computing a variable value from a response.
Yet another thing that might appear useful would be possibility to retry certain call until a user-defined condition is met, maybe specify it in a similar way that assertions are specified. Of course here we would need to be able to set time limits and inter-call delays.
Together these features would allow for more complex scenarios with objects having their state changed by some background tasks.
The text was updated successfully, but these errors were encountered:
I'd like to propose an externsion to the testing feature.
Since the spec
.yml
file essentially maps to a linear chain of calls, it would be useful sometimes to alter the execution order of those queries.For example, if some call fails an assertion there might not make much sense to run the rest of the call chain. This could be signalled somehow in the tests section.
Another case when further execution may better be stopped is when there's been a problem with computing a variable value from a response.
Yet another thing that might appear useful would be possibility to retry certain call until a user-defined condition is met, maybe specify it in a similar way that assertions are specified. Of course here we would need to be able to set time limits and inter-call delays.
Together these features would allow for more complex scenarios with objects having their state changed by some background tasks.
The text was updated successfully, but these errors were encountered: