On the Effectiveness of Modular Testing in EvoSuite
summary
EvoSuite’s modular mode forbids non-target setup calls and often produces tiny prefixes, so a fork named EMOTE relaxes that constraint to allow class-level methods during generation while forcing test prefixes to end with the target method and changing fitness to count only branches reached via the target call chain. With a 120-second search budget per method EMOTE finds 304 additional branches and yields a 15.15% average branch-coverage improvement across the SF100 subset compared to vanilla EvoSuite.
AI-written summary · about
chapters (7)
- 0:00Modular testing with EvoSuite
- 1:39EvoSuite’s testing mode limits
- 3:21Prefix constraints in EvoSuite
- 6:28EMoT and relaxed prefix generation
- 7:30EMoT’s test cluster challenges
- 9:36EMoT evaluation on SF100
- 12:49Q&A on EMoT’s fitness
related talks
37mGenerating JUnit test cases Automatically with Evosuite
38mMutants to the rescue: How effective are your unit tests?
01h 00mKill Evil Mutants!
24mGain more confidence in your code with mutation testing
29mWho is testing the test?
41mHow deep are your tests
14mCompatible Branch Coverage Driven Symbolic Execution for Efficient Bug Finding
24mWho is testing your tests?