scholarly journals SPLMT-TE: A Software Product Lines System Test Case Tool

2012 ◽  
Author(s):  
Crescencio Rodrigues Lima Neto ◽  
Eduardo S. Almeida ◽  
Silvio R. L. Meira
Keyword(s):  
Software Testing ◽  
Software Product Lines ◽  
Test Case ◽  
Product Lines ◽  
Case Tool ◽  
Software Products ◽  
Test Execution ◽  
Testing Tools ◽  
Software Product ◽  
Testing Tool

The product lines approach requires specific testing tools that should help to manage reusable testing assets and automate the test execution. Despite of the increasing interest by the research community regarding software testing tools, Software Products Lines (SPL) still need tools to support the testing process. This work presents briefly the results of a mapping study on software testing tool and defines the requirements, design and implementation of a software product lines system test case tool, aiming at the creation and management of test assets. A controlled experiment was also conducted to evaluate the tool effectiveness.

scholarly journals CyberSPL: A Framework for the Verification of Cybersecurity Policy Compliance of System Configurations Using Software Product Lines

2019 ◽  
Vol 9 (24) ◽  
pp. 5364 ◽  
Author(s):  
Ángel Jesús Varela-Vaca  ◽  
Rafael M. Gasca ◽  
Rafael Ceballos ◽  
María Teresa Gómez-López ◽  
Pedro Bernáldez Torres
Keyword(s):  
Automated Analysis ◽  
Software Product Lines ◽  
Product Line ◽  
Feature Models ◽  
Product Lines ◽  
Software Products ◽  
Wide Range ◽  
Proposal A ◽  
Software Product ◽  
Real Scenario

Cybersecurity attacks affect the compliance of cybersecurity policies of the organisations. Such disadvantages may be due to the absence of security configurations or the use of default configuration values of software products and systems. The complexity in the configuration of products and systems is a known challenge in the software industry since it includes a wide range of parameters to be taken into account. In other contexts, the configuration problems are solved using Software Product Lines. This is the reason why in this article the framework Cybersecurity Software Product Line (CyberSPL) is proposed. CyberSPL is based on a methodology to design product lines to verify cybersecurity policies according to the possible configurations. The patterns to configure the systems related to the cybersecurity aspects are grouped by defining various feature models. The automated analysis of these models allows us to diagnose possible problems in the security configurations, reducing or avoiding them. As support for this proposal, a multi-user and multi-platform solution has been implemented, enabling setting a catalogue of public or private feature models. Moreover, analysis and reasoning mechanisms have been integrated to obtain all the configurations of a model, to detect if a configuration is valid or not, including the root cause of problems for a given configuration. For validating the proposal, a real scenario is proposed where a catalogue of four different feature models is presented. In this scenario, the models have been analysed, different configurations have been validated, and several configurations with problems have been diagnosed.

scholarly journals Efficient Regression Testing of Software Product Lines by Reducing Redundant Test Executions

2020 ◽  
Vol 10 (23) ◽  
pp. 8686
Author(s):  
Pilsu Jung ◽  
Sungwon Kang ◽  
Jihyun Lee
Keyword(s):  
Product Family ◽  
Software Product Lines ◽  
Product Line ◽  
Regression Testing ◽  
Test Case ◽  
Test Cases ◽  
Product Lines ◽  
Test Selection ◽  
Software Product ◽  
Regression Test

Regression testing for software product lines (SPLs) is challenging because it must ensure that all the products of a product family work correctly whenever changes are made. One approach to reducing the cost of regression testing is the regression test selection (RTS), which selects a subset of regression test cases. However, even when RTS is applied, SPL regression testing can still be expensive because, in the product line context, each test case can be executed on more than one product that reuses the test case, which would typically result in a large number of test executions. A promising direction is to eliminate redundant test executions of test cases. We propose a method that, given a test case, identifies a set of products, on which the test case will cover the same sequence of source code statements and produce the same testing results, and then excludes these products from products to apply the test case to. The evaluation results showed that when the full selection approach and the approach of repetitively applying an RTS method for a single software system are used for test selection, our method reduced, respectively, 59.3% and 40.0% of the numbers of test executions of the approaches.

scholarly journals Statically Analyzing the Energy Efficiency of Software Product Lines

2021 ◽  
Vol 11 (1) ◽  
pp. 13
Author(s):  
Marco Couto ◽  
João Paulo Fernandes ◽  
João Saraiva
Keyword(s):  
Energy Consumption ◽  
Simulated Annealing Algorithm ◽  
Traditional Approach ◽  
Software Product Lines ◽  
Product Lines ◽  
Worst Case ◽  
Software Products ◽  
Important Concern ◽  
Software Product ◽  
Development Approach

Optimizing software to become (more) energy efficient is an important concern for the software industry. Although several techniques have been proposed to measure energy consumption within software engineering, little work has specifically addressed Software Product Lines (SPLs). SPLs are a widely used software development approach, where the core concept is to study the systematic development of products that can be deployed in a variable way, e.g., to include different features for different clients. The traditional approach for measuring energy consumption in SPLs is to generate and individually measure all products, which, given their large number, is impractical. We present a technique, implemented in a tool, to statically estimate the worst-case energy consumption for SPLs. The goal is to reason about energy consumption in all products of a SPL, without having to individually analyze each product. Our technique combines static analysis and worst-case prediction with energy consumption analysis, in order to analyze products in a feature-sensitive manner: a feature that is used in several products is analyzed only once, while the energy consumption is estimated once per product. This paper describes not only our previous work on worst-case prediction, for comprehensibility, but also a significant extension of such work. This extension has been realized in two different axis: firstly, we incorporated in our methodology a simulated annealing algorithm to improve our worst-case energy consumption estimation. Secondly, we evaluated our new approach in four real-world SPLs, containing a total of 99 software products. Our new results show that our technique is able to estimate the worst-case energy consumption with a mean error percentage of 17.3% and standard deviation of 11.2%.

scholarly journals CASE Tool Support for Variability Management in Software Product Lines

2017 ◽  
Vol 50 (1) ◽  
pp. 1-45 ◽  
Author(s):  
Rabih Bashroush ◽  
Muhammad Garba ◽  
Rick Rabiser ◽  
Iris Groher ◽  
Goetz Botterweck
Keyword(s):  
Software Product Lines ◽  
Tool Support ◽  
Product Lines ◽  
Case Tool ◽  
Software Product ◽  
Variability Management
Sign in / Sign up

Export Citation Format

Share Document