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
It is difficult to fix a problem without being able to reproduce it.However, reproducing a problem i...
Abstract—In this work we present TacoPlug, an Eclipse plug-in that lets users explore error traces o...
This repository contains the data used in our paper entitled ["On the impact of release policies on ...
This technical note provides an extended description of a paper titled 'Does Unit-Tested Code Crash?...
We have mined the Eclipse bug and version databases to map failures to Eclipse components. The resul...
AbstractThe analysis of bug databases reveals that some software components are far more failure-pro...
this paper do not immediately exhibit themselves and are often discovered after deploymen
In this paper we look at the Eclipse IDE and its support for CDT (C/C++ Development Tools). Eclipse ...
A widely shared belief in the software engineering community is that stack traces are much sought af...
In this paper we look at the Eclipse IDE and its support for CDT (C/C++ Development Tools). Eclipse ...
Software monitoring systems have high performance overhead because they typically monitor all proces...
A dataset with over 200.000 reported bugs extracted from the Eclipse and Mozilla projects (respectiv...
<p>We present three defect rediscovery datasets mined from Bugzilla. The datasets capture data for t...
We investigate the relationship between faults and five of Fowler et al.'s least-studied smells in c...
Abstract—A widely shared belief in the software engineering community is that stack traces are much ...
It is difficult to fix a problem without being able to reproduce it.However, reproducing a problem i...
Abstract—In this work we present TacoPlug, an Eclipse plug-in that lets users explore error traces o...
This repository contains the data used in our paper entitled ["On the impact of release policies on ...
This technical note provides an extended description of a paper titled 'Does Unit-Tested Code Crash?...
We have mined the Eclipse bug and version databases to map failures to Eclipse components. The resul...
AbstractThe analysis of bug databases reveals that some software components are far more failure-pro...
this paper do not immediately exhibit themselves and are often discovered after deploymen
In this paper we look at the Eclipse IDE and its support for CDT (C/C++ Development Tools). Eclipse ...
A widely shared belief in the software engineering community is that stack traces are much sought af...
In this paper we look at the Eclipse IDE and its support for CDT (C/C++ Development Tools). Eclipse ...
Software monitoring systems have high performance overhead because they typically monitor all proces...
A dataset with over 200.000 reported bugs extracted from the Eclipse and Mozilla projects (respectiv...
<p>We present three defect rediscovery datasets mined from Bugzilla. The datasets capture data for t...
We investigate the relationship between faults and five of Fowler et al.'s least-studied smells in c...
Abstract—A widely shared belief in the software engineering community is that stack traces are much ...
It is difficult to fix a problem without being able to reproduce it.However, reproducing a problem i...
Abstract—In this work we present TacoPlug, an Eclipse plug-in that lets users explore error traces o...
This repository contains the data used in our paper entitled ["On the impact of release policies on ...