https://bz.apache.org/bugzilla/show_bug.cgi?id=59152
--- Comment #10 from Vladimir Sitnikov <[email protected]> --- Milamber>It's very easy to conclude that this load test is successful (only 25% errors on 1 page), but in reality, this is a bad load test, because my target load is reduce to 25%, and the target server have been tested with only at 75% of the load. Technically speaking, "validation" of a test report should include not only "% of errors" validation, but "planned throughput vs actual throughput", "planned response times vs actual response times". If a test is hard to setup (e.g. lots of steps), then it might be better to start new iteration to try one's best to achieve "throughput goal". At the end of the day, real users do restart from scratch in case of failure. Note: high failrate would be misleading, since it will show "consequence", while it makes much more sense in knowing "root cause". In that case, it would be good to restart after the first failure, and %error would show exactly the step that failed. -- You are receiving this mail because: You are the assignee for the bug.
