Replies: 1 comment
-
I think you can. I hope that does not cause any problems.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm in the middle of writing a test for #15333 and I need to provide several different responses to the same request that is repeatedly retried to ensure that pieces of responses can be formed back together into one. The
swsbounce
option I thought would be ideal but from examiningserver.response
data I can see it allows only a single different response.For example if I have response data in
<data>
that contains the keywordswsbounce
then for the retry request the test script will use the response data in<data1>
. However if data1 contains the keywordswsbounce
then for the next request the test script loops back to<data>
instead of what I would have expected<data2>
.In other words I end up with responses in this order:
<data>
,<data1>
,<data>
,<data1>
,<data>
,<data1>
, etcBut this is what I want:
<data>
,<data1>
,<data2>
,<data3>
,<data4>
, etchere's an example of how swsbounce normally works, taken from a random test:
curl/tests/data/test519
Lines 9 to 42 in 75a2079
As far as I can tell, there is never a data2 in these cases. Can I change swsbounce behavior in the script to not reset back to 0 (ie
<data>
) can anyone forsee problems with this? Or should I add a new keyword? It's unclear who implemented this behavior.edit: See #16085 for the proposed fix.
Beta Was this translation helpful? Give feedback.
All reactions