Dataset Open Access

Does Unit-Tested Code Crash? A Case Study of Eclipse

Chioteli Efstathia; Batas Ioannis; Spinellis Diomidis


Dublin Core Export

<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:creator>Chioteli Efstathia</dc:creator>
  <dc:creator>Batas Ioannis</dc:creator>
  <dc:creator>Spinellis Diomidis</dc:creator>
  <dc:date>2019-01-22</dc:date>
  <dc:description>
	The "jacoco.xml" file contains the code coverage of Eclipse Project generated by JaCoCo
	The "incidents (stack traces).zip" file contains the stacktraces files (in JSON format) with the specific popular release and product that we used for our research.
	All The Eclipse stacktraces can be downloaded here.
	The "output.csv" contains the data that we produced after combining JaCoCo Report and stacktraces.
</dc:description>
  <dc:identifier>https://zenodo.org/record/2546790</dc:identifier>
  <dc:identifier>10.5281/zenodo.2546790</dc:identifier>
  <dc:identifier>oai:zenodo.org:2546790</dc:identifier>
  <dc:language>eng</dc:language>
  <dc:relation>doi:10.5281/zenodo.2546789</dc:relation>
  <dc:rights>info:eu-repo/semantics/openAccess</dc:rights>
  <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
  <dc:subject>unit-testing, crash reports, code coverage, stack traces, JaCoCo, software reliability</dc:subject>
  <dc:title>Does Unit-Tested Code Crash?  A Case Study of Eclipse</dc:title>
  <dc:type>info:eu-repo/semantics/other</dc:type>
  <dc:type>dataset</dc:type>
</oai_dc:dc>
274
97
views
downloads
All versions This version
Views 274273
Downloads 9797
Data volume 8.5 GB8.5 GB
Unique views 241240
Unique downloads 6464

Share

Cite as