@conference {Ahmed:2014:IAC:2641580.2641585,
	title = {The Impact of Automatic Crash Reports on Bug Triaging and Development in Mozilla},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1:1{\textendash}1:8},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Free/Open Source Software projects often rely on users submitting bug reports. However, reports submitted by novice users may lack information critical to developers, and the process may be intimidating and difficult. To gather more and better data, projects deploy automatic crash reporting tools, which capture stack traces and memory dumps when a crash occurs. These systems potentially generate large volumes of data, which may overwhelm developers, and their presence may discourage users from submitting traditional bug reports. In this paper, we examine Mozilla{\textquoteright}s automatic crash reporting system and how it affects their bug triaging process. We find that fewer than 0.00009\% of crash reports end up in a bug report, but as many as 2.33\% of bug reports have data from crash reports added. Feedback from developers shows that despite some problems, these systems are valuable. We conclude with a discussion of the pros and cons of automatic crash reporting systems.
},
	keywords = {Automatic Crash reporting, debugging, FOSS, Free/Open Source Software, Open Bug Reporting, testing},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641585},
	url = {http://doi.acm.org/10.1145/2641580.2641585},
	author = {Ahmed, Iftekhar and Mohan, Nitin and Jensen, Carlos}
}
@article {1323,
	title = {OSS-TMM},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {1 - 22},
	abstract = {Open Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test \& Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products.},
	keywords = {testing},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011040101},
	author = {Morasca, Sandro and Taibi, Davide and Tosi, Davide}
}
