6] to calculate the suspiciousness of each executable statement as the detected priority.
likelihood of containing the bug) of each executable statement.
4) The output [mathematical expression not reproducible] reflects the probability that executable statement [s.
3) Construct the virtual test set with twelve test cases and ensure that each test case only covers one executable statement.
4) Input the virtual test set into the trained DNN model and get the suspiciousness value of each corresponding executable statement, and then rank the statements according to their suspiciousness values.
Since the DNN-based fault localization technique, Tarantula localization technique, and PPDG localization technique all produce a suspiciousness value ranking list for executable statements, we adopt the EXAM score as the evaluation criterion to measure the effectiveness.
Table 6 provides the detailed introduction of the seven C programs in Siemens suite, including the program name, number of faulty versions of each program, number of statement lines, number of executable statements lines, and the number of test cases.
d) The difference between the correct versions and the faulty versions is not included in executable statements of program and cannot be replaced.
As the executable statements of Siemens suite programs are only about hundreds of lines, the scale and complexity of the software have increased gradually and the program may be of as many as thousands or ten thousands of lines.
As the executable statements of Siemens suite programs are only about hundreds of lines, we further verify the effectiveness of DNN-based fault localization technique in large-scale datasets.