Skip to Main Content
To constantly test software, in order to keep it as free as possible from defects, it is required to find and apply a testing approach that best fits the product under test. The variety of problems and the richness of existing approaches make the challenge to choose and plan for a better combination to reach desired quality level even harder. This paper introduces a case study that aims presenting different test coverage values according to the used approach. The context of our study considers the application of structure-based techniques on a Java ME software product line, which makes testing even more critical due to software complexity. In this work we present code coverage analysis and evaluation of main differences between data flow and control flow techniques, considering the use of a test tool and the reuse of test assets in different software versions from a software product line.