Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
A Systematic Mapping of Test Case Generation Techniques Using UML Interaction Diagrams
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0001-8177-4355
UIIT PMAS Arid Agriculture University, PAK.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0002-1532-8223
Capital University of Science and Technology, PAK.
2020 (English)In: Journal of Software: Evolution and Process, ISSN 2047-7473, E-ISSN 2047-7481, Vol. 32, no 6, article id e2235Article, review/survey (Refereed) Published
Abstract [en]

Testing plays a vital role for assuring software quality. Among the activities performed during testing process, test cases generation is a challenging and labor intensive task. Test case generation techniques based on UML models are getting the attention of researchers and practitioners. This study provides a systematic mapping of test case generation techniques based on interaction diagrams. The study compares the test case generation techniques, regarding their capabilities and limitations, and it also assesses the reporting quality of the primary studies. It has been revealed that UML interaction diagrams based techniques are mainly used for integration testing. The majority of the techniques are using sequence diagrams as input models, while some are using collaboration. A notable number of techniques are using interaction diagram along with some other UML diagram for test case generation. These techniques are mainly focusing on interaction, scenario, operational, concurrency, synchronization and deadlock related faults.

From the results of this study, we can conclude that the studies presenting test case generation techniques using UML interaction diagrams failed to illustrate the use of rigorous methodology, and these techniques did not demonstrate the empirical evaluation in an industrial context. Our study revealed the need for tool support to facilitate the transfer of solutions to industry.

Place, publisher, year, edition, pages
John Wiley & Sons, 2020. Vol. 32, no 6, article id e2235
Keywords [en]
Software testing, Test case generation, Interaction diagrams, Model based testing, Systematic mapping
National Category
Computer Systems Software Engineering
Identifiers
URN: urn:nbn:se:bth-17363DOI: 10.1002/smr.2235ISI: 000503853200001Scopus ID: 2-s2.0-85076917532OAI: oai:DiVA.org:bth-17363DiVA, id: diva2:1267008
Projects
EASE - Embedded Applications Software Engineering
Funder
Vinnova, 2015-03235Available from: 2018-11-30 Created: 2018-11-30 Last updated: 2021-12-16Bibliographically approved
In thesis
1. Regression Testing Challenges and Solutions: An Industry-Academia Perspective
Open this publication in new window or tab >>Regression Testing Challenges and Solutions: An Industry-Academia Perspective
2019 (English)Licentiate thesis, comprehensive summary (Other academic)
Abstract [en]

Background: Software quality assurance (QA) is an essential activity in the software development lifecycle. Among the different QA activities, regression testing is a challenging task for large-scale software development. Regression testing is a well-researched area, and a large number of techniques have been proposed to fulfill the needs of industry. Despite the extensive research, the adoption of proposed regression testing techniques in the industry is limited. Studies show that there is a visible gap between research and practice.

Objective: This work aims at reducing the gap between industry and academia in regression testing. To fulfill this aim we have the following objectives:

1) Understanding the practitioners' goals regarding regression testing.

2) Understanding the current state of regression testing practice and challenges in the industry.

3) Investigating the testing research applicable in an industrial context.

Method: We conducted multiple studies using different methods.

To explore the industry perspective on regression testing we used focus group and interview-based studies. To explore solutions from the literature, we used the systematic literature review and systematic mapping study.

Results: This thesis presents the practitioners' specific regression testing goals. The identified goals are confidence, controlled fault slippage, effectiveness, efficiency, and customer satisfaction. The challenges identified in the thesis are of two categories, 1) management related challenges and 2) technical challenges. Technical challenges relate to test suite maintenance, test case selection, test case prioritization, evaluation of regression testing.

We have mapped 26 empirically evaluated regression testing techniques to the context, effect, and information taxonomies, and provided a guide to the practitioners regarding the adoption of the techniques in an industrial setting. We have also classified 56 model-based test case generation techniques regarding their strengths/limitations, input/intermediate models used, and relevance to the industrial context.

Conclusions: The challenges identified in this study are not new for research and practice. There could be two reasons regarding the presence of recurring challenges: 1) regression testing techniques proposed in the literature do not fit the companies’ context, 2) or, companies are not aware of the availability of the techniques that could be suitable for their context. To support the adoption of existing research on regression testing in the industry, we have presented three taxonomies. These taxonomies, allow the characterization of regression testing techniques and enable to determine which of these techniques might be suitable in a given context. Furthermore, the identification of information needs for these techniques would be helpful to learn the implications regarding the cost of adoption. Regarding the support in test case generation, we conclude that current research on interaction model-based test case generation techniques did not illustrate the use of rigorous methodology, and currently, model-based test case generation techniques have low relevance for the industrial problems.

Place, publisher, year, edition, pages
Karlskrona, Sweden: Blekinge Tekniska Högskola, 2019. p. 146
Series
Blekinge Institute of Technology Licentiate Dissertation Series, ISSN 1650-2140 ; 2
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17381 (URN)978-91-7295-365-9 (ISBN)
Presentation
2019-01-08, J1650, Campus Gräsvik, Karlskrona, 14:00 (English)
Opponent
Supervisors
Funder
VINNOVA, 2015-03235
Available from: 2018-12-06 Created: 2018-12-05 Last updated: 2019-01-17Bibliographically approved

Open Access in DiVA

fulltext(292 kB)1217 downloads
File information
File name FULLTEXT02.pdfFile size 292 kBChecksum SHA-512
2e6f9a69c2aebc7fe86836e3c9778ca0d13fcde72f3327ecc093921b5bd015bab2d47bce66ae0cbf22fb4234257a174917e432605d51e153c9976fd6b789f5aa
Type fulltextMimetype application/pdf

Other links

Publisher's full textScopus

Authority records

Minhas, Nasir MehmoodPetersen, Kai

Search in DiVA

By author/editor
Minhas, Nasir MehmoodPetersen, Kai
By organisation
Department of Software Engineering
In the same journal
Journal of Software: Evolution and Process
Computer SystemsSoftware Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 1314 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 660 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf