Can We Spot Energy Regressions using ...
Document type :
Compte-rendu et recension critique d'ouvrage
Title :
Can We Spot Energy Regressions using Developers Tests?
Author(s) :
Danglot, Benjamin [Auteur]
Falleri, Jean-Rémy [Auteur]
Laboratoire Bordelais de Recherche en Informatique [LaBRI]
Rouvoy, Romain [Auteur]
Self-adaptation for distributed services and large software systems [SPIRALS]
Falleri, Jean-Rémy [Auteur]
Laboratoire Bordelais de Recherche en Informatique [LaBRI]
Rouvoy, Romain [Auteur]

Self-adaptation for distributed services and large software systems [SPIRALS]
Journal title :
Empirical Software Engineering
Publisher :
Springer Verlag
Publication date :
2024-07-25
ISSN :
1382-3256
HAL domain(s) :
Informatique [cs]
English abstract : [en]
Background Software Energy Consumption (SEC) is gaining more and more attention. In this paper, we tackle the problem of warning developers about the increase of SEC of their programs during Continuous Integration (CI). ...
Show more >Background Software Energy Consumption (SEC) is gaining more and more attention. In this paper, we tackle the problem of warning developers about the increase of SEC of their programs during Continuous Integration (CI). Objective In this study, we investigate if the CI can leverage developers' tests to perform energy regression testing. Energy regression is similar to performance regression but focuses on the energy consumption of the program instead of standard performance indicators, like execution time or memory consumption. Method We perform an exploratory study of the usage of developers' tests for energy regression testing. We first investigate if developers' tests can be used to obtain stable SEC indicators. Then, we evaluate if comparing the SEC of developers' tests between two versions can pinpoint energy regressions introduced by automated program mutations. Finally, we manually evaluate several real commits pinpointed by our approach. Impact Our study will pave the way for automated SEC regression tools that can be readily deployed inside an existing CI infrastructure to raise awareness of SEC issues among practitioners.Show less >
Show more >Background Software Energy Consumption (SEC) is gaining more and more attention. In this paper, we tackle the problem of warning developers about the increase of SEC of their programs during Continuous Integration (CI). Objective In this study, we investigate if the CI can leverage developers' tests to perform energy regression testing. Energy regression is similar to performance regression but focuses on the energy consumption of the program instead of standard performance indicators, like execution time or memory consumption. Method We perform an exploratory study of the usage of developers' tests for energy regression testing. We first investigate if developers' tests can be used to obtain stable SEC indicators. Then, we evaluate if comparing the SEC of developers' tests between two versions can pinpoint energy regressions introduced by automated program mutations. Finally, we manually evaluate several real commits pinpointed by our approach. Impact Our study will pave the way for automated SEC regression tools that can be readily deployed inside an existing CI infrastructure to raise awareness of SEC issues among practitioners.Show less >
Language :
Anglais
Popular science :
Non
Collections :
Source :
Files
- document
- Open access
- Access the document
- _EMSE__Can_We_Spot_Energy_Regression_using_Developers_Tests_-2.pdf
- Open access
- Access the document
- document
- Open access
- Access the document
- _EMSE__Can_We_Spot_Energy_Regression_using_Developers_Tests_-2.pdf
- Open access
- Access the document