A Framework for Checking Regression Test Selection Tools
Regression test selection (RTS) reduces regression testing costs by re-running only tests that can change behavior due to code changes. To deal with the rapidly growing costs of regression testing, several RTS tools were recently developed and adopted by researchers and large software organizations. As RTS tools gain adoption, it becomes critical to check that they are correct and efficient. Unfortunately, checking RTS tools currently relies solely on limited sets of tests that RTS tool developers write.
We present RTSCheck , the first framework for checking RTS tools. RTSCheck feeds evolving programs (i.e., sequences of program revisions) to an RTS tool and checks the output against rules inspired by existing RTS test suites; violations of these rules are likely to be due to deviations from expected RTS tool behavior. RTSCheck uses three components to obtain evolving programs: (1) AutoEP automatically generates evolving programs and corresponding tests; (2) DefectsEP uses buggy and fixed program revisions from bug databases; and (3) EvoEP uses sequences of program revisions from actual histories of open-source projects. We use RTSCheck to check three recently developed RTS tools for Java: Clover, Ekstazi, and STARTS. RTSCheck discovered 27 bugs in the tools. Each RTSCheck component helped discover different bugs in all three RTS tools.
Wed 29 May (GMT-04:00) Eastern Time (US & Canada) change
|16:00 - 16:20|
Improving Test Effectiveness Using Test Executions History: An Industrial Experience ReportSEIPIndustry Program
|16:20 - 16:40|
FastLane: Test Minimization for Rapidly Deployed Large-scale Online ServicesTechnical TrackIndustry Program
|16:40 - 17:00|
Emilio CrucianiGran Sasso Science Institute, L'Aquila, Italy, Breno MirandaFederal University of Pernambuco, Roberto VerdecchiaGran Sasso Science Institute, Vrije Universiteit Amsterdam, Antonia BertolinoCNR-ISTIPre-print
|17:00 - 17:20|
|17:20 - 17:40|
|17:40 - 17:50|
|17:50 - 18:00|