1 / 6

Regression Testing

Continuous Systematic Testing of Evolving Software. Regression Testing. Mary Jean Harrold , Darko Marinov , Stephen Oney, Mauro Pezze , Adam Porter, John Penix , Per Runeson, Shin Yoo. Open Problems. Cost/benefit Which test cases are worth executing and when?

red
Download Presentation

Regression Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Continuous Systematic Testing of Evolving Software Regression Testing Mary Jean Harrold, Darko Marinov, Stephen Oney, Mauro Pezze, Adam Porter, John Penix, Per Runeson, ShinYoo

  2. Open Problems • Cost/benefit • Which test cases are worth executing and when? • Cost for setup vs execution, creating configurations vs execution etc • Non-functional testing; levels of testing • Data infrastructure • Which data is needed to select test cases systematically? • For today’s methods? For tomorrow’s? • Technical solutions • Selection/prioritization/extension/deletion • Repairing test cases and oracles • Anonymizations and retesting, Concurrency retesting

  3. Promising direction • Gathering and using information that is there already: • changes, code, test cases, executions, configurations, defect reports…

  4. Collaboration • Baseline by sharing previous research • Start by two recent reviews (Yoo, Runeson) • Apply techniques to industry and OSS data • Run ”shadow projects” in multiple domains

  5. Paper titles [1] ”Introducing countinous systematic testing of evolving software” IEEE SW 2010 • Guidance to bits and pieces that need to be in place to get it to work. Cases: ABB, Microsoft, Google [2] ”Cost in the loop of countinous systematic testing of evolving software”, IEEE TSE 2014 • Cost model based test selection

  6. Funding Project:Cost in the loop of Countinous And Systematic Testing of evoLving Software - CASTLeS MARK HARMAN HENRY MUCCINI WOLFRAM SCHULTE TAO XIE

More Related