Upgrade to Pro — share decks privately, control downloads, hide ads and more …

On The Limits of Mutation Reduction Strategies

On The Limits of Mutation Reduction Strategies

Mutation analysis is a key technique in software test suite evaluation. However, it is expensive to run, and numerous techniques have been developed to reduce the mutans to be evaluated.
This research describes a theoretical and empirical investigation into strategies such as operator selection and stratified sampling, and their effectiveness in improving the quality of mutants produced.

Rahul Gopinath

May 19, 2016
Tweet

More Decks by Rahul Gopinath

Other Decks in Research

Transcript

  1. On The Limits of Mutation Reduction Strategies Rahul Gopinath Amin

    Alipour Iftekhar Ahmed Carlos Jensen Alex Groce
  2. And so is the number of bugs The number of

    vulnerabilities per year (1999 - 2016) [cvedetails.com] Hitomi : Lost in space because of a bug
  3. We rely on testing. But… •  Tests are written mostly

    manually [lam2014beyond] •  Tests may have complex control flow, and may use external resources [lam2014beyond]. •  Subject to similar problems of correctness as programs.
  4. We rely on testing. But… •  Graph coverage criteria are

    often used. But are they useful? •  Depends on how good your assertions are [zhang-fse15] •  Assertions have a tendency to be inadequate: •  Up to 65% unit tests in OSS Projects sampled have inadequate asserts [zhi-issta13]. class SimpleName def initialize(num) @x = num end def add(y) @x + y end def multiply(y) @x * y end end class TestSimpleNumber < Test::Unit::TestCase def setup @num = SimpleNumber.new(2) end def test_simple_add assert(@num.add(2) != 0) end def test_simple_multiply assert(@num.multiply(2) != @num) end end
  5. ? What is mutation analysis? •  Generates fake bugs that

    look like the real things •  Used in the industry as a stopping criteria for test suite development •  Used by researchers to generate real looking faults, and then judge the effec=veness of tes=ng techniques. •  Researchers have shown that mutants are similar to bugs [just2014], and their detectability is similar to real faults [andrews2005] and tests with high muta=on score is beIer able to detect hand seeded faults [le2009] than other test coverage metrics.
  6. Mutation Analysis Determinis=cally insert exhaus've first order faults against which

    test suites can be judged. •  The # of mutants produced for even small programs is huge. •  Each mutant requires a potential full test suite run. Δ=b2 – 4ac d = b^2 + 4 * a * c; d = b^2 * 4 * a * c; d = b^2 / 4 * a * c; d = b^2 ^ 4 * a * c; d = b^2 % 4 * a * c; d = b^2 << 4 * a * c; d = b^2 >> 4 * a * c; d = b^2 * 4 + a * c; d = b^2 * 4 - a * c; d = b^2 * 4 / a * c; d = b^2 * 4 ^ a * c; d = b^2 * 4 % a * c; d = b^2 * 4 << a * c; d = b^2 * 4 >> a * c; d = b^2 * 4 * a + c; d = b^2 * 4 * a - c; d = b^2 * 4 * a / c; d = b^2 * 4 * a ^ c; d = b^2 * 4 * a % c; d = b^2 * 4 * a << c; d = b^2 * 4 * a >> c; d = b + 2 - 4 * a * c; d = b - 2 - 4 * a * c; d = b * 2 - 4 * a * c; d = b / 2 - 4 * a * c; d = b % 2 - 4 * a * c; d = b << 2 - 4 * a * c; d = b >> 2 - 4 * a * c; d = b^0 - 4 * a * c; d = b^1 - 4 * a * c; d = b^-1 - 4 * a * c; d = b^MAX - 4 * a * c; d = b^MIN - 4 * a * c; d = b - 4 * a * c; d = b ^ 4 * a * c; d = b^2 - 0 * a * c; d = b^2 - 1 * a * c; d = b^2 – (-1) * a * c; d = b^2 - MAX * a * c; d = b^2 - MIN * a * c; d = b^2 * a * c; d = b^2 - a * c;
  7. Smarter (Parallelizing) Mutation Analysis •  Many approaches to reduce the

    computational time requirements of mutation analysis Time Fewer (Selective) Faster (Optimizing) Original [harman2011,offutt2000]
  8. Mutation Analysis : Mutation Selection •  Operator Selection: •  Constrained

    Mutation [mathur91] •  Selective Mutation [offutt93] •  Program Element Strata: •  Sampling by Program Element [gligoric2013] •  Clustering: •  Static [patrick2014] •  Dynamic [offutt2014] •  Domain [hussain2008] Do fewer strategies:
  9. Do Fewer: Improvement from intelligent selection. What is the maximum

    improvement that we can hope for over random sampling? Utility = % improvement in unique mutants over random sampling same number of mutants..
  10. Do Fewer: Improvement from intelligent selection. What is the maximum

    utility for a given strategy? •  Empirical analysis •  Theoretical analysis
  11. Finding maximum utility: Compare with minimal mutants •  We compared

    the best N mutants with oracular knowledge (minimal set) with N randomly sampled mutants The best reduction strategy is minimal mutant (you already know which mutant is killed by which test).
  12. Comparison of perfect and random sampling : Empirical •  Found

    the minimal set of mutants from each project (rerun 100 times) •  Generated random comparison mutant set of same size. •  Computed the utility using minimal mutants.
  13. The distribution of utility •  Mean utility 13.1% •  95%

    projects have maximum utility between {12.23, 14.26} (u-test p<0.01)
  14. Is this the best that we can do? Theoretical Analysis:

    We start with a few simplifications: •  Every non-redundant mutant can be killed uniquely by some test case. •  Equal number of redundant mutants for each mutant. These are simplifications that help us to derive a theory for limits.
  15. Comparison of perfect strategy and random sampling N mutants k

    unique mutants Perfect set of s mutants k unique with p each k p Unique mutants : k < ~ 58.2% Randomly sampled s mutants Unique mutants :
  16. Summary •  We empirically computed the utility of a perfect

    strategy for picking minimal mutants over random sampling, finding it to be less than 15%. •  We theoretically computed the utility of a perfect strategy over random sampling, assuming uniform distribution of redundancy, finding a maximum of 58%. •  The assumptions made, such as a unique test case for each unique mutant, may not be available in a given test site. Hence the difference between theory and empirical analysis. •  The take-home point is that there is a hard limit to the amount of improvement one can expect from any intelligent mutation reduction over random sampling.
  17. However.... •  The utility for perfect strategy •  What happens

    when the heuristic of reduction technique fails? •  Worst case: duplicates of a single mutant. •  U is no longer bounded. Caveat: Under the conditions of uniform distribution of mutants.
  18. •  Instead of reduction, add new operators, and reduce by

    sampling. •  New formulation: X : new unique mutants. •  In the best case, X increases with new mutagens (unbounded). •  Worst case: Same as random sampling. However.... Entire mutant population (before sampling) Entire mutant population (before sampling) Caveat: Under the conditions of uniform distribution of mutants.
  19. Conclusions •  Mutation reduction strategies: •  Very little potential gain

    •  High potential for harm •  New mutation operators: •  High potential for gain •  Little potential for harm •  Want better mutants? •  Avoid mutation reduction strategies •  Investigate newer mutation operators