The Experts below are selected from a list of 20850 Experts worldwide ranked by ideXlab platform
Benoit Baudry - One of the best experts on this subject based on the ideXlab platform.
-
test them all is it worth it assessing configuration sampling on the jhipster web development stack
Empirical Software Engineering, 2019Co-Authors: Axel Halin, Alexandre Nuttinck, Mathieu Acher, Xavier Devroey, Gilles Perrouin, Benoit BaudryAbstract:Many approaches for testing Configurable software Systems start from the same assumption: it is impossible to test all configurations. This motivated the definition of variability-aware abstractions and sampling techniques to cope with large configuration spaces. Yet, there is no theoretical barrier that prevents the exhaustive testing of all configurations by simply enumerating them if the effort required to do so remains acceptable. Not only this: we believe there is a lot to be learned by Systematically and exhaustively testing a Configurable System. In this case study, we report on the first ever endeavour to test all possible configurations of the industry-strength, open source Configurable software System JHipster, a popular code generator for web applications. We built a testing scaffold for the 26,000+ configurations of JHipster using a cluster of 80 machines during 4 nights for a total of 4,376 hours (182 days) CPU time. We find that 35.70% configurations fail and we identify the feature interactions that cause the errors. We show that sampling strategies (like dissimilarity and 2-wise): (1) are more effective to find faults than the 12 default configurations used in the JHipster continuous integration; (2) can be too costly and exceed the available testing budget. We cross this quantitative analysis with the qualitative assessment of JHipster’s lead developers.
-
test them all is it worth it assessing configuration sampling on the jhipster web development stack
arXiv: Software Engineering, 2017Co-Authors: Axel Halin, Alexandre Nuttinck, Mathieu Acher, Xavier Devroey, Gilles Perrouin, Benoit BaudryAbstract:Many approaches for testing Configurable software Systems start from the same assumption: it is impossible to test all configurations. This motivated the definition of variability-aware abstractions and sampling techniques to cope with large configuration spaces. Yet, there is no theoretical barrier that prevents the exhaustive testing of all configurations by simply enumerating them, if the effort required to do so remains acceptable. Not only this: we believe there is lots to be learned by Systematically and exhaustively testing a Configurable System. In this case study, we report on the first ever endeavour to test all possible configurations of an industry-strength, open source Configurable software System, JHipster, a popular code generator for web applications. We built a testing scaffold for the 26,000+ configurations of JHipster using a cluster of 80 machines during 4 nights for a total of 4,376 hours (182 days) CPU time. We find that 35.70% configurations fail and we identify the feature interactions that cause the errors. We show that sampling strategies (like dissimilarity and 2-wise): (1) are more effective to find faults than the 12 default configurations used in the JHipster continuous integration; (2) can be too costly and exceed the available testing budget. We cross this quantitative analysis with the qualitative assessment of JHipster's lead developers.
Axel Halin - One of the best experts on this subject based on the ideXlab platform.
-
test them all is it worth it assessing configuration sampling on the jhipster web development stack
Empirical Software Engineering, 2019Co-Authors: Axel Halin, Alexandre Nuttinck, Mathieu Acher, Xavier Devroey, Gilles Perrouin, Benoit BaudryAbstract:Many approaches for testing Configurable software Systems start from the same assumption: it is impossible to test all configurations. This motivated the definition of variability-aware abstractions and sampling techniques to cope with large configuration spaces. Yet, there is no theoretical barrier that prevents the exhaustive testing of all configurations by simply enumerating them if the effort required to do so remains acceptable. Not only this: we believe there is a lot to be learned by Systematically and exhaustively testing a Configurable System. In this case study, we report on the first ever endeavour to test all possible configurations of the industry-strength, open source Configurable software System JHipster, a popular code generator for web applications. We built a testing scaffold for the 26,000+ configurations of JHipster using a cluster of 80 machines during 4 nights for a total of 4,376 hours (182 days) CPU time. We find that 35.70% configurations fail and we identify the feature interactions that cause the errors. We show that sampling strategies (like dissimilarity and 2-wise): (1) are more effective to find faults than the 12 default configurations used in the JHipster continuous integration; (2) can be too costly and exceed the available testing budget. We cross this quantitative analysis with the qualitative assessment of JHipster’s lead developers.
-
test them all is it worth it assessing configuration sampling on the jhipster web development stack
arXiv: Software Engineering, 2017Co-Authors: Axel Halin, Alexandre Nuttinck, Mathieu Acher, Xavier Devroey, Gilles Perrouin, Benoit BaudryAbstract:Many approaches for testing Configurable software Systems start from the same assumption: it is impossible to test all configurations. This motivated the definition of variability-aware abstractions and sampling techniques to cope with large configuration spaces. Yet, there is no theoretical barrier that prevents the exhaustive testing of all configurations by simply enumerating them, if the effort required to do so remains acceptable. Not only this: we believe there is lots to be learned by Systematically and exhaustively testing a Configurable System. In this case study, we report on the first ever endeavour to test all possible configurations of an industry-strength, open source Configurable software System, JHipster, a popular code generator for web applications. We built a testing scaffold for the 26,000+ configurations of JHipster using a cluster of 80 machines during 4 nights for a total of 4,376 hours (182 days) CPU time. We find that 35.70% configurations fail and we identify the feature interactions that cause the errors. We show that sampling strategies (like dissimilarity and 2-wise): (1) are more effective to find faults than the 12 default configurations used in the JHipster continuous integration; (2) can be too costly and exceed the available testing budget. We cross this quantitative analysis with the qualitative assessment of JHipster's lead developers.
Volke Aumgarte - One of the best experts on this subject based on the ideXlab platform.
-
an industrial academic Configurable System on chip project csoc coarse grain xpp leon based architecture integration
Design Automation and Test in Europe, 2003Co-Authors: Jurge Ecke, M Vorbach, Alexande Thomas, Volke AumgarteAbstract:Summary form only given. This paper describes the actual status and results of a dynamically Configurable System-on-Chip (CSoC) integration, consisting of a SPARC-compatible Leon processor-core, a commercial coarse-grain XPP-array of suitable size from PACT Informationstechnologie AG, and application-tailored global/local memory topology with efficient Amba-based communication interfaces. The given adaptive architecture is synthesized within an industrial/academic SoC project onto 0.18 and 0.13 /spl mu/m UMC CMOS technologies at Universitaet Karlsruhe (TH). Due to exponential increasing CMOS mask costs, essential aspects for the industry are now adaptivity of SoCs, which can be realized by integrating reConfigurable re-usable hardware parts on different granularities into Configurable Systems-on-Chip (CSoCS).
Jurge Ecke - One of the best experts on this subject based on the ideXlab platform.
-
an industrial academic Configurable System on chip project csoc coarse grain xpp leon based architecture integration
Design Automation and Test in Europe, 2003Co-Authors: Jurge Ecke, M Vorbach, Alexande Thomas, Volke AumgarteAbstract:Summary form only given. This paper describes the actual status and results of a dynamically Configurable System-on-Chip (CSoC) integration, consisting of a SPARC-compatible Leon processor-core, a commercial coarse-grain XPP-array of suitable size from PACT Informationstechnologie AG, and application-tailored global/local memory topology with efficient Amba-based communication interfaces. The given adaptive architecture is synthesized within an industrial/academic SoC project onto 0.18 and 0.13 /spl mu/m UMC CMOS technologies at Universitaet Karlsruhe (TH). Due to exponential increasing CMOS mask costs, essential aspects for the industry are now adaptivity of SoCs, which can be realized by integrating reConfigurable re-usable hardware parts on different granularities into Configurable Systems-on-Chip (CSoCS).
-
architecture memory and interface technology integration of an industrial academic Configurable System on chip csoc
IEEE Computer Society Annual Symposium on VLSI, 2003Co-Authors: Jurge Ecke, M VorbachAbstract:This paper describes the actual status and results of a dynamically Configurable System-on-chip (CSoC) integration, consisting of a SPAR C-compatible LEON processor-core, a commercial coarse-grain XPP-array of suitable size from PACT XPP Technologies AG, and application-tailored global/local memory topology with efficient Amba-based communication interfaces. The given adaptive architecture is synthesized within an industrial/academic SoC project onto 0.18 and 0.13 /spl mu/m UMC CMOS technologies at Universitaet Karlsruhe (TH). Due to exponentially increasing CMOS mask costs, essential aspects for the industry are now adaptivity of SoCs, which can be realized by integrating reConfigurable re-usable hardware parts on different granularities into Configurable Systems-on-chip (CSoCs).
Wolfgang Schroderpreikschat - One of the best experts on this subject based on the ideXlab platform.
-
feature consistency in compile time Configurable System software facing the linux 10 000 feature problem
European Conference on Computer Systems, 2011Co-Authors: Wolfgang SchroderpreikschatAbstract:Much System software can be configured at compile time to tailor it with respect to a broad range of supported hardware architectures and application domains. A good example is the Linux kernel, which provides more than 10,000 Configurable features, growing rapidly. From the maintenance point of view, compile-time configurability imposes big challenges. The configuration model (the selectable features and their constraints as presented to the user) and the configurability that is actually implemented in the code have to be kept in sync, which, if performed manually, is a tedious and error-prone task. In the case of Linux, this has led to numerous defects in the source code, many of which are actual bugs. We suggest an approach to automatically check for configurability-related implementation defects in large-scale Configurable System software. The configurability is extracted from its various implementation sources and examined for inconsistencies, which manifest in seemingly conditional code that is in fact unconditional. We evaluate our approach with the latest version of Linux, for which our tool detects 1,776 configurability defects, which manifest as dead/superfluous source code and bugs. Our findings have led to numerous source-code improvements and bug fixes in Linux: 123 patches (49 merged) fix 364 defects, 147 of which have been confirmed by the corresponding Linux developers and 20 as fixing a new bug.