Table 2 |
||||
|
The results of testing SeqMap with MT |
||||
|
MRs |
Original |
SM8 |
SM11 |
SM18 |
|
|
||||
|
MR1(a) |
1,2,3,4,5 |
1,2,3,4,5 |
1,4,5 |
|
|
MR1(b) |
1,2,3 |
1,2,3,4,5 |
5 |
|
|
MR1(c) |
1,2,3,4,5 |
1,2,3,4,5 |
1,4 |
|
|
MR2(a) |
1,2,3,4,5 |
1,2,3,4,5 |
||
|
MR2(b) |
1,2,3,4,5 |
1,2,5 |
||
|
MR3(a) |
1,2,3,4,5 |
1,2,3,4,5 |
1,4,5 |
|
|
MR3(b) |
1,3,4,5 |
1,2,3,4,5 |
||
|
MR4(a) |
2,3,4,5 |
1,2,3,4,5 |
1,2,3,4,5 |
|
|
MR4(b) |
1,2,3,4,5 |
1,2,3,4,5 |
||
|
|
||||
|
SeqMap and three of its mutants were tested against five batches of test cases, which are labeled as 1, 2, 3, 4 and 5. Each pair of test cases that detects a violation of a MR in a program is labeled by its batch in the respective cell in the table. For example, the label '1,4' in the cell [SM18, MR1(c)] indicates that SM18 violates MR1(c) according to the test cases in batch 1 and batch 4. |
||||
|
Chen et al. BMC Bioinformatics 2009 10:24 doi:10.1186/1471-2105-10-24 |
||||