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
The check and cross on the http_req_failed line is the opposite of what I expected. The number after the check actually refers to responses where http_req_failed is true, whereas I expected ✓ to mean "HTTP code as expected" and ✗ to mean "HTTP code not as expected".
I think this is confusing and suggest either flipping that behavior or clarifying with "y failed z expected".
The text was updated successfully, but these errors were encountered:
And having a default hook for http_req_failed that would print our custom Rate text. That way users can re-use it for printing their own metrics in a custom manner, or for removing certain metrics out of the summary altogether, while still having the the jslib code handle the majority of the work
The check and cross on the
http_req_failed
line is the opposite of what I expected. The number after the check actually refers to responses wherehttp_req_failed
is true, whereas I expected ✓ to mean "HTTP code as expected" and ✗ to mean "HTTP code not as expected".I think this is confusing and suggest either flipping that behavior or clarifying with "y failed z expected".
The text was updated successfully, but these errors were encountered: