It seems like it should be possible to write a sequential replay test where I can match rules, but record multiple interactions per rule set. This would help by not enforcing strict ordering of requests like a pure sequential test, but would allow repeated queries to an endpoint with differing responses each time.
It seems like the best behavior for this type of test would be to record rules to tape as long as READ_WRITE is active and then parse the rules when READ_ONLY is active. You would consume the rules sequentially until only one is left and then reuse it for all future requests which match that rule set.
I'm not sure how hard this would be. I may take a look at implementing it.
It seems like it should be possible to write a sequential replay test where I can match rules, but record multiple interactions per rule set. This would help by not enforcing strict ordering of requests like a pure sequential test, but would allow repeated queries to an endpoint with differing responses each time.
It seems like the best behavior for this type of test would be to record rules to tape as long as READ_WRITE is active and then parse the rules when READ_ONLY is active. You would consume the rules sequentially until only one is left and then reuse it for all future requests which match that rule set.
I'm not sure how hard this would be. I may take a look at implementing it.