Closed dinurp closed 1 year ago
@dinurp Actually, it already works as it is designed. The idea of repeat
is to quickly send several requests at the same time and thus put the server under load. These are not treated as own requests, but are merged at the end in the body of the first request. In the JSON output, I output the body only as a string and these contain the timings that you are interested in. For this reason it would be better for you to simply use `--output body' here.
I noticed that the timings are not properly merged in the '--json' output . The root element contains only the first timings object. I change this and output the average. And additionally I make it possible that the timings are also output when using --output exchange
or --output timings
.
Thanks for pointing me to the right direction. I see that I can get what I was looking for by parsing the body.
httpyac send post.http -n post--repeat 25 --json > out.json
jq "[.requests[].response.body|fromjson|.responses[]|{statusCode,timings}]" out.json
I am trying to find the response times of repeated request. I saw that the timings in the response would be useful for this.
httpyac send post.http -n post --repeat 2 --repeat-mode serial > .\post-log.json
after cleaning up the file,But, if I try to use the option --json to get the response in a easily parsed format, the output does not contain the responses from repeated requests. It only contains one response.
httpyac send post.http -n post --repeat 2 --repeat-mode serial --json > .\post-log.json
Note: the field is now named
response
and notresponses
Also, with release 5.2.1 as fix for issue https://github.com/httpyac/httpyac.github.io/issues/34, fields
count
andstatusCount
were added to the summary. These are also lost if the formatting option --json is used.