This dataset accompanies the article ICPE 2016 "Learning from Source Code History to Identify Performance Regressions". This dataset provides the source code and runtime metrics associated with 17 Pharo applications. Further information about this dataset can be found in the README.txt file
Context: Software development projects involve the use of a wide range of tools to produce a softwar...
The development cycle of large software is necessarily prone to introducing software errors that are...
Traditional means of gathering performance data are trac-ing, which is limited by the available stor...
The objective of this work is to improve look up for changes in source code performance and help to ...
This is the dataset and source code of the paper: On the Detection of Performance Regression Introdu...
Context. Software testing is the process of finding faults in software while executing it. The resul...
Predicting likely software defects in the future is valuable for project managers when planning reso...
The quality of code can be measured using source code metrics. Looking at the trends of these metric...
In this paper, we describe the extraction of source code metrics from the Jazz repository and the ap...
Regression testing can be done by re-executing a test suite on different software versions and compa...
As a software application is developed and maintained, changes to the source code may cause unintent...
Software projects go through a phase of maintenance and, in case of open source projects, through ha...
This paper presents a scenario-based approach for the evaluation of the quality attribute of perform...
1. The spreadsheet "Perf Issue Empirical Data Package.xlsx" contains the details of data extraction...
Even the addition of a single extra field or control statement in the source code of a large-scale s...
Context: Software development projects involve the use of a wide range of tools to produce a softwar...
The development cycle of large software is necessarily prone to introducing software errors that are...
Traditional means of gathering performance data are trac-ing, which is limited by the available stor...
The objective of this work is to improve look up for changes in source code performance and help to ...
This is the dataset and source code of the paper: On the Detection of Performance Regression Introdu...
Context. Software testing is the process of finding faults in software while executing it. The resul...
Predicting likely software defects in the future is valuable for project managers when planning reso...
The quality of code can be measured using source code metrics. Looking at the trends of these metric...
In this paper, we describe the extraction of source code metrics from the Jazz repository and the ap...
Regression testing can be done by re-executing a test suite on different software versions and compa...
As a software application is developed and maintained, changes to the source code may cause unintent...
Software projects go through a phase of maintenance and, in case of open source projects, through ha...
This paper presents a scenario-based approach for the evaluation of the quality attribute of perform...
1. The spreadsheet "Perf Issue Empirical Data Package.xlsx" contains the details of data extraction...
Even the addition of a single extra field or control statement in the source code of a large-scale s...
Context: Software development projects involve the use of a wide range of tools to produce a softwar...
The development cycle of large software is necessarily prone to introducing software errors that are...
Traditional means of gathering performance data are trac-ing, which is limited by the available stor...
DOI
Add to ORKG