Replies: 8 comments
-
Same question. |
Beta Was this translation helpful? Give feedback.
-
What kind of instrumented line in the question? Did you mean each line of source code (json_parser.c), or instrumented coverage function in the json_parser.instrumented.ll file? |
Beta Was this translation helpful? Give feedback.
-
@RiceBiscuits I mean a source code. I collected whole instrumented lines from source code and the number of them seems to be under 500. Does the number of lines in evaluation criteria refer to the number of covered lines in |
Beta Was this translation helpful? Give feedback.
-
covered line in the evaluation criteria means *.cov file's line count except duplicated line. |
Beta Was this translation helpful? Give feedback.
-
But doesn't the *.cov files only include the coverage of the last executed seed and not the total coverage? |
Beta Was this translation helpful? Give feedback.
-
@RiceBiscuits If I consider the same line number of source code with different column numbers as different cases, I got 679 cases using only seed_1.json and seed_2.json without implementing mutate and update_seeds functions. So can I get 20 points out of 20 coverage points for json parser without implementing mutate and update_seeds? Below is my coverage. Thank you! 😀
|
Beta Was this translation helpful? Give feedback.
-
It seems that there some confusion. Let me clarify.
|
Beta Was this translation helpful? Give feedback.
-
@h2oche @kimjungwow Check the issue #110! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
According to evaluation criteria, we should cover over 500 lines to get full score. However, when I measured the total number of instrumented lines of given JSON parser, I think it is under 500. Did I do something wrong?
Beta Was this translation helpful? Give feedback.
All reactions