Multi-level Tests for Model Driven Web Applications

Fraternali, Piero; Tisi, Massimo

doi:10.1007/978-3-642-13911-6_11

Cited by 7 publications

(17 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…T A B L E 1 Summary of search rounds (in round 0, studies P0003, P0004 and P0005 are listed in selected backward column just for convenience; these were the original seeds upon which we started the snowballing process). P0383 [45] • Forward snowballing: We analysed 12 forward citations to this study in March 2018 and another 12 in February 2020. None were selected.…”

Section: Search Iterations and Resultsmentioning

confidence: 99%

“…Similar to Fraternali and Tisi [45], [44] exploited a model‐to‐model transformation of UML models to UML Testing Profile models, from which test cases for the model level are generated. Subsequently, model‐to‐text transformations automatically produce test cases in a variety of languages; examples are test scripts that follow the JUnit style.…”

Section: Analysis Based On the Research Questionsmentioning

confidence: 99%

“…In additional round (from experts), studies are listed in columns related to backward snowballing for convenience. For discussing RQ1, we grouped the 23 studies listed in the first line of Table 4 as follows: studies that directly provided information regarding the transformation of test cases across the abstraction levels by describing the tool that supports the transformation [16,17,20,24,[31][32][33]36,46], studies that described procedures for transforming test cases from models to code [25,34,[38][39][40][41]44,45,47] and studies that just reported that test cases developed at the model level are then applied to test the code [21][22][23]26,43]. Studies from the three groups are discussed in the sequence.…”

Section: Analysis Based On the Research Questionsmentioning

confidence: 99%

See 2 more Smart Citations

On transforming model‐based tests into code: A systematic literature review

Ferrari,

Durelli,

Andler

et al. 2023

Software Testing Verif & Rel

View full text Add to dashboard Cite

SummaryModel‐based test design is increasingly being applied in practice and studied in research. Model‐based testing (MBT) exploits abstract models of the software behaviour to generate abstract tests, which are then transformed into concrete tests ready to run on the code. Given that abstract tests are designed to cover models but are run on code (after transformation), the effectiveness of MBT is dependent on whether model coverage also ensures coverage of key functional code. In this article, we investigate how MBT approaches generate tests from model specifications and how the coverage of tests designed strictly based on the model translates to code coverage. We used snowballing to conduct a systematic literature review. We started with three primary studies, which we refer to as the initial seeds. At the end of our search iterations, we analysed 30 studies that helped answer our research questions. More specifically, this article characterizes how test sets generated at the model level are mapped and applied to the source code level, discusses how tests are generated from the model specifications, analyses how the test coverage of models relates to the test coverage of the code when the same test set is executed and identifies the technologies and software development tasks that are on focus in the selected studies. Finally, we identify common characteristics and limitations that impact the research and practice of MBT: (i) some studies did not fully describe how tools transform abstract tests into concrete tests, (ii) some studies overlooked the computational cost of model‐based approaches and (iii) some studies found evidence that bears out a robust correlation between decision coverage at the model level and branch coverage at the code level. We also noted that most primary studies omitted essential details about the experiments.

show abstract

Section: Search Iterations and Resultsmentioning

confidence: 99%

Section: Analysis Based On the Research Questionsmentioning

confidence: 99%

Section: Analysis Based On the Research Questionsmentioning

confidence: 99%

See 1 more Smart Citation

On transforming model‐based tests into code: A systematic literature review

Ferrari,

Durelli,

Andler

et al. 2023

Software Testing Verif & Rel

View full text Add to dashboard Cite

show abstract

“…Testing (including early testing) and maintenance were not addressed in the first generation of MDWE proposals but were later discussed in several approaches [35,57,69]; a thorough survey can be found in [20].…”

Section: Life Cycle Coveragementioning

confidence: 99%

25 Years of Model-Driven Web Engineering: What we achieved, What is missing

Rossi¹,

Urbieta²,

Distante

et al. 2016

CLEIej

View full text Add to dashboard Cite

Model-Driven Web Engineering (MDWE) approaches aim to improve the Web applications development process by focusing on modeling instead of coding, and deriving the running application by transformations from conceptual models to code. The emergence of the Interaction Flow Modeling Language (IFML) has been an important milestone in the evolution of Web modeling languages, indicating not only the maturity of the field but also a final convergence of languages. In this paper we explain the evolution of modeling and design approaches since the early years (in the 90’s) detailing the forces which drove that evolution and discussing the strengths and weaknesses of some of those approaches. A brief presentation of the IFML is accompanied with a thorough analysis of the most important achievements of the MDWE community as well as the problems and obstacles that hinder the dissemination of model-driven techniques in the Web engineering field.

show abstract

“…IFML is now a standard by the Object Management Group (OMG) that is inspired by WebML's notation [59]. IFML also benefitted from the application of WebML in several projects [143,144,177]. The IFML specification has five main technical artefacts [59]:…”

Section: Ifml Overviewmentioning

confidence: 99%

Using models to support the search-based testing of web applications

Yasin¹

View full text Add to dashboard Cite

A web application model offers a high-level description of a web application's behaviour. Using the web application's model to derive test cases serves as a good starting point in testing, since the model is created based on the web application's specification. To improve the capabilities of the derived test cases in revealing faults in the web application's behaviour, these test cases can be improved using search-based testing. In this thesis, we propose a search-based testing approach that explores a large search space of possible combinations of a web application's behaviour. The approach evolves an initial set of model-based test cases to produce more test cases that are more effective in finding failures in the web application's behaviour. Firstly, we present a pseudo-Genetic Algorithm that evolves a set of model-based test cases by mutating or recombining their model-based genes to obtain a set of model-based offspring test cases. The algorithm transforms the offspring test cases into executable test cases. We incorporate the pseudo-Genetic Algorithm in a search-based testing tool called MutateIFML. We describe the model-based test representation which uses the Interaction Flow Modelling Language to model the test cases and the system under test. We define the mutation score of the population as the fitness function for MutateIFML. Secondly, we validate MutateIFML's capability and applicability using two web applications: OpenBiblio and RosarioSIS. We discuss our results and the achievements of MutateIFML in producing effective test cases that are measured by the capability of the population in killing faults that are seeded into these web applications. The validation of the approach reveals that enhancing the single fitness function with a coverage indicator can help in guiding the selection phase of the search-based testing approach. We discover MutateIFML's limitation in scaling up to larger more complicated web applications due to the initial manual task of fault-seeding, the absence of a suitable automated support tool for the testing framework and the complexities of MutateIFML. We then extend the single fitness function used in MutateIFML to include branch coverage. We validate the improved multi-objective fitness function with a small case study that focuses on a module of a web application to examine the viability of the multi-objective fitness function in killing additional mutant systems under test. Although the multiobjective fitness function is able to kill additional mutants, we realise that it can cause MutateIFML's testing cost to increase substantially. Finally, we suggest possible directions for future work. Financial support Scholarship support from the Ministry of Higher Education Malaysia (MoHE) and Universiti Tun Hussein Onn Malaysia (UTHM) in Malaysia is gratefully acknowledged. Temporary scholarship support and financial assistance from the

show abstract

Multi-level Tests for Model Driven Web Applications

Cited by 7 publications

References 17 publications

On transforming model‐based tests into code: A systematic literature review

On transforming model‐based tests into code: A systematic literature review

25 Years of Model-Driven Web Engineering: What we achieved, What is missing

Using models to support the search-based testing of web applications

Contact Info

Product

Resources

About