1. Toward Dependable Software: Cyberinfrastructure Support for Controlled Experimentation with Testing and Analysis Techniques Gregg Rothermel and Matt Dwyer Computer Science and Engineering

2. Software Dependability Dependability: fitness for intended use Avionics GUIs Device Drivers Spreadsheets

3. Software Testing & Program Analysis Techniques Achieving Dependability Program Supporting Data void add(Object o) { buffer[head] = o; head = (head+1)%size; } Object take() { … tail=(tail+1)%size; return buffer[tail]; } Requirement 1: … Requirement 2: … … Dependability Information Dependability Information

4. Code Coverage-Based Testing Software Testing Program Testing Requirements void add(Object o) { buffer[head] = o; head = (head+1)%size; } Object take() { … tail=(tail+1)%size; return buffer[tail]; } Test Results Report Test Results Report

5. Model Checker Model Checking OK Error trace or Finite-state model Temporal logic formula ( ! } )( ! } )

6. Essential (Empirical) Questions 1.Is a given technique more cost-effective than other techniques? 2.What factors influence the relative cost- effectiveness of techniques? 3.What models best capture the cost- benefits tradeoffs between techniques?

7. Experimentation Treatment T1 Subject A Subject B Cure & Side-Effects Information Cure & Side-Effects Information Treatment T2 Subject C Subject D Cure & Side-Effects Information Cure & Side-Effects Information

8. Experimentation with Testing and Analysis Techniques Technique T1 Program A Program B Dependability & Cost Information Dependability & Cost Information Technique T2 Program C Program D Dependability and Cost Information Dependability and Cost Information

9. State of the Art In a survey of top journals/conferences: –41% of papers included empirical studies - 17% included controlled experiments –1% involved shared artifacts

10. State of the Art In a survey of top journals/conferences: –41% of papers included empirical studies - 17% included controlled experiments –1% involved shared artifacts As empiricists, in the testing & analysis sub-field, we have not evolved far.

11. Requirements for Empirical Research on Testing & Analysis Prepared experiment “subjects” Adequate computational resources Community engagement Knowledge of empirical study design

12. Requirements for Empirical Research on Testing & Analysis Prepared experiment “subjects” Adequate computational resources Community engagement Knowledge of empirical study design

13. Experiment “Subjects” Experiments with testing and analysis require various “subjects”, or artifacts Obtaining, preparing, organizing and sharing artifacts is expensive and difficult Until recently, obtaining support for these efforts has been difficult

14. NSF Support NSF CRI program (Research Resources) $1.1 million, 4 year collaborative grant Investigators: –University of Nebraska – Lincoln: Gregg Rothermel (PI) Sebastian Elbaum Matt Dwyer –Kansas State University: John Hatcliff (PI)

15. Project Goal Create and disseminate a repository of software-related artifacts sufficient to support rigorous controlled experimentation with testing and analysis techniques across the broad community of software engineering researchers and educators

16. Proposed Artifacts Code bases for C and Java applications Supporting elements: –e.g., versions, faults, requirements, behavior specifications, models, test inputs Basic static and dynamic data: –e.g., expected outputs, fault-exposure data, coverage patterns Mechanisms for accessing data: –e.g, filters and access routines

17. Requirements for Empirical Research on Testing & Analysis Prepared experiment “subjects” Adequate computational resources Community engagement Knowledge of empirical study design

18. Obstacles to Efficient Execution of Empirical Studies Controlled experiments with testing & analysis techniques require significant computational resources Programs and test suites may be long running, e.g., one study took 8 months to collect data Program analysis techniques may require large amounts of memory, e.g., studies run on 32-bit architectures regularly used 4 Gbytes. Archiving analysis data may require significant storage, e.g., run-time trace data for a single study can easily use 100s of Gbytes

19. ARO and UNL Support to Overcome these Obstacles ARO DURIP program $400,000 equipment grant Investigators: –University of Nebraska – Lincoln: Matt Dwyer (PI) –Kansas State University John Hatcliff (PI) UNL startup funding for Rothermel and Dwyer Dept. staff support for Research Computing

20. Hardware Infrastructure 2.1 Tbyte disk storage array 45 node dual-Opteron 248 Cluster –32 nodes have 16 Gbytes of RAM –12 nodes have 4 Gbytes of RAM –Running linux, Sun Grid Engine Remote access to 12 node quad-Opteron 246 Cluster at Kansas State

21. Early Adopters Studies of cost/effectiveness of extracting unit tests from system tests Studies of probe placement for run-time monitoring Studies of heuristic strategies for model checking concurrent programs Studies of heuristic search strategies for test suite generation Trace data collection to characterize server applications to predict “pre-crash” states Experiments on reducing the cost of inferring program specifications

22. Requirements for Empirical Research on Testing & Analysis Prepared experiment “subjects” Adequate computational resources Community engagement Knowledge of empirical study design

23. Supporting the Emerging Experimental Community A growing understanding that computing is an experimental discipline –45 experts support our efforts –More education in experimental methods needed Initial repository of subjects –Distributed via web-site –Full-time staff will develop and maintain site –We will populate repository with a wide-range of sample subjects

24. Repository Lifespan We are planning for the repository to serve the community well-beyond the grant duration Exploring ideas such as –Open-source model for repository contributions and maintenance –Building consensus in community that subject development is valuable –Use of conference/workshop model for review of contributions

25. Summary Testing and analysis are essential for software dependability – which is essential for everything Progress in testing/analysis has been limited by lack of empirical research Empirical software research is hard and requires –subjects, computational resources, community consensus, and knowledge of empirical methods Our current efforts are focused on supporting researchers on the first three of these

26. Looking Forward A significant remaining challenge is supporting scientists in the design of experiments –Decision-support for empirical studies –Requires development of knowledge base and tools to query/synthesize that knowledge –Scott Henninger (UNL) is leading work in this area Ultimately, our goal is to see that research on software systems develops into a discipline whose experimental maturity matches its theoretical maturity

27. Toward Dependable Software: Cyberinfrastructure Support for Controlled Experimentation with Testing and Analysis Techniques Gregg Rothermel and Matt Dwyer Computer Science and Engineering