-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to understand the statistics output file #795
Labels
Comments
Hi,
|
I am sorry, it is still not clear to me. Just to be sure, so evomaster only counts the number of endpoints that have 500 error and doesn't count the number of unique requests/payloads that cause 500 error? Or does distinct500Faults actually describe the number of unique requests/payloads that cause 500 error? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I have question regarding the statistics file.
I have used evomaster to fuzz my simple application that has 3 endpoints. After the fuzzing was done, I checked my application log and there were many requests causing internal server error (500).
When I check the generated statistics file, it shows only 3 errors5xx and 3 distinct500Faults. Does this mean that even if there are many 500 errors on 1 endpoint, they are still counted as 1 error?
Here it is my statistics file content:
The text was updated successfully, but these errors were encountered: