Automating Test Case Selection in Model-Based Software Product Line Development

Knapp, Alexander; Roggenbach, Markus; Schlingloff, Bernd-Holger
April 2015
International Journal of Software & Informatics;2015, Vol. 9 Issue 2, p153
Academic Journal
We address the problem of how to select test cases for products in a controlled model-based software product line development process. CVL, the common variability language, gives a framework for materialisation of product models from a given base model, variability model and resolution model. From such product models, software products can be derived. In practise, test case development for the product line often is independent from the product development. Therefore, the problem arises which test cases can be applied to which products. In particular, the question is whether a test case for one specific product can be also used for a "similar" product. In this paper, we show how the expected outcome of a test case to a product in a model-based software product line development can be determined. That is, we give a procedure for assigning the outcome of a given test case on an arbitrary member of a software product line. We recall the relevant definitions for software product line engineering, describe our approach, and demonstrate it with the example of a product line of super-automatic espresso machines.


Related Articles

  • Long-Term Testing in a Short-Term World. Rokosz, Vaughn T. // IEEE Software;May/Jun2003, Vol. 20 Issue 3, p64 

    Focuses on the complexities in doing system testing for computer software products. Scheduled functions included in many software systems; Reason of software developers for applying accelerated stress testing; Advantages of the Good Enough Quality approach.

  • Don't pay for software testing cuts. Michaels, Paul // Computer Weekly;6/10/2008, p20 

    The article offers the author's comments on why software testing is an important mechanism. Customers and suppliers need to adopt a consistent approach to software development and implementation. They need to be prepared to invest sufficient resources, optimize pre-existing modules and factor...

  • Incorporating Performance Testing in Test-Driven Development. Johnson, Michael J.; Maximilien, E. Michael; Chih-Wei Ho; Williams, Laurie // IEEE Software;May/Jun2007, Vol. 24 Issue 3, p67 

    The article focuses on a study regarding incorporation of performance testing in test-driven development (TDD). To incorporate performance testing into a TDD process, the researchers designed two sets of performance test cases. One set could finish quickly and provide early warning of...

  • The Coding Never Stops.  // InfoWorld;3/12/2007, Vol. 29 Issue 11, p44 

    The author relates his experience of writing software code. The owners of the company the author worked for told the developers of their new duty to create a new product for Christmas and wanted to start beta testing in four months. His boss wrote the specifications herself instead of finding a...

  • Integrating Testing and Implementation into Development. Pyhäjärvi, Maaret; Rautiainen, Kristian // Engineering Management Journal;Mar2004, Vol. 16 Issue 1, p33 

    Cost of defects increases significantly the later the defects are found. Testing is the means to find defects, and we view testing in the broader perspective of maximizing customer satisfaction and providing feedback for process refinement, in addition to just detecting and getting defects...

  • Dynamic risk control for project development. Gasparini, Mauro; Margaria, Gabriella; Wynn, Henry P. // Statistical Methods & Applications;2004, Vol. 13 Issue 1, p73 

    A statistical methodology for dynamic risk control is discussed. The research is aimed at constructing tools for the analysis of expert opinions within a company about the risks involved in the production of a new commercial product or service. Focus is on risk events and on the analysis of the...

  • Putting Apps to the Test. Berg, Andrew // Wireless Week;9/1/2009, Vol. 15 Issue 7, p6 

    The article discusses the need for software developers to subject their softwares into a series of tests before releasing them to the market to prevent revenue loss in the U.S. According to Stephen King, chief executive officer (CEO) of Mob4Hire, the release of untested software out to the...

  • SMA - THE SMYLE MODELING APPROACH. BOLLIG, Benedikt; KATOEN, Joost-Pieter; KERN, Carsten; LEUCKER, Martin // Computing & Informatics;2010, Vol. 29 Issue 1, p45 

    This paper introduces the model-based software development lifecycle model SMA -- the Smyle Modeling Approach -- which is centered around Smyle. Smyle is a dedicated learning procedure to support engineers to interactively obtain design models from requirements-characterized as either being...

  • letters. Curran, Tim; Phillips, Mark // CRN;1/3/2005, Issue 1127, p25 

    Presents letters to the editor referencing articles and topics discussed in previous issues. "Real Values," which presented an outlook for trends in the computer industry in the U.S. in 2005; Open-source developments in Microsoft Corp.; Efforts of Microsoft to seek beta-testers for its Office...


Read the Article


Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics