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
Complete IOCO Test Cases: A Case Study
University of Sao Paolo, São Carlos, Brazil.
University of Sao Paolo, São Carlos, Brazil.
Halmstad University, School of Information Technology, Halmstad Embedded and Intelligent Systems Research (EIS), Centre for Research on Embedded Systems (CERES).
Halmstad University, School of Information Technology, Halmstad Embedded and Intelligent Systems Research (EIS), Centre for Research on Embedded Systems (CERES).ORCID iD: 0000-0002-4869-6794
2016 (English)In: A-TEST 2016 - Proceedings of the 7th International Workshop on Automating Test Case Design, Selection, and Evaluation, co-located with FSE 2016, New York, NY: ACM Press, 2016, p. 38-44Conference paper, Published paper (Refereed)
Abstract [en]

Input/Output Transition Systems (IOTSs) have been widely used as test models in model-based testing. Traditionally, input output conformance testing (IOCO) has been used to generate random test cases from IOTSs. A recent test case generation method for IOTSs, called Complete IOCO, applies fault models to obtain complete test suites with guaranteed fault coverage for IOTSs. This paper measures the efficiency of Complete IOCO in comparison with the traditional IOCO test case generation implemented in the JTorX tool. To this end, we use a case study involving five specification models from the automotive and the railway domains. Faulty mutations of the specifications were produced in order to compare the efficiency of both test generation methods in killing them. The results indicate that Complete IOCO is more efficient in detecting deep faults in large state spaces while IOCO is more efficient in detecting shallow faults in small state spaces. © 2016 ACM.

Place, publisher, year, edition, pages
New York, NY: ACM Press, 2016. p. 38-44
Keywords [en]
Conformance testing, Input output conformance (IOCO), Complete input output conformance, Mealy input output transition systems, fault models
National Category
Computer and Information Sciences
Identifiers
URN: urn:nbn:se:hh:diva-33212DOI: 10.1145/2994291.2994297Scopus ID: 2-s2.0-85007035449ISBN: 978-1-4503-4401-2 (print)OAI: oai:DiVA.org:hh-33212DiVA, id: diva2:1071791
Conference
7th International Workshop on Automating Test Case Design, Selection, and Evaluation (A-TEST 2016), Seattle, WA, USA, November 18, 2016
Projects
VR Project EFFEMBACKKS Project AUTO-CAAS
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile CommunicationsSwedish Research Council, 621-2014-5057Knowledge Foundation, 20140312
Note

The research of S. C. Paiva and A. Simao have been supported by Sao Paulo Research Foundation (Grants 2012/09650-5 and 2012/02232-3), Coordination for the Improvement of Higher Education Personnel and National Counsel of Technological and Scientic Development.

Available from: 2017-02-06 Created: 2017-02-06 Last updated: 2018-03-23Bibliographically approved
In thesis
1. Test Models and Algorithms for Model-Based Testing of Software Product Lines
Open this publication in new window or tab >>Test Models and Algorithms for Model-Based Testing of Software Product Lines
2017 (English)Licentiate thesis, comprehensive summary (Other academic)
Abstract [en]

Software product line (SPL) engineering has become common practice for mass production and customization of software. A software product line comprises a family of software systems which share a managed core set of artifacts. There are also a set of well-defined variabilities between the products of a product line. The main idea in SPL engineering is to enable systematic reuse in different phases of software development to reduce cost and time to release.

Model-Based Testing (MBT) is a technique that is widely used for checking the quality of software systems. In MBT, test cases are generated from an abstract model, which captures the desired behavior of the system. Then, the test cases are executed against a real implementation of the system and the compliance of the implementation to the specification is checked by comparing the observed outputs with the ones prescribed by the model.

Software product lines have been applied in many domains in which sys- tems are mission critical and MBT is one of the techniques that is widely used for quality assurance of such systems. As the number of products can be potentially large in an SPL, using conventional approaches for MBT of the products of an SPL individually and as single systems can be very costly and time consuming. Hence, several approaches have been proposed in order to enable systematic reuse in different phases of the MBT process.

An efficient modeling technique is the first step towards an efficient MBT technique for SPLs. There have been several formalisms proposed for modeling SPLs. In this thesis, we conduct a study on such modeling techniques, focusing on three fundamental formalisms, namely featured transition systems, modal transition systems, and product line calculus of communicating systems. We compare the expressive power and the succinctness of these formalisms.

Furthermore, we investigate adapting existing MBT methods for efficient testing of SPLs. As a part of this line of our research, we adapt the test case generation algorithm of one of the well-known black-box testing approaches, namely, Harmonized State Identification (HSI) method by exploiting the idea of delta-oriented programming. We apply the adapted test case generation algorithm to a case study taken from industry and the results show up to 50 percent reduction of time in test case generation by using the delta-oriented HSI method.

In line with our research on investigating existing MBT techniques, we compare the relative efficiency and effectiveness of the test case generation algorithms of the well-known Input-Output Conformance (ioco) testing approach and the complete ioco which is another testing technique used for input output transition systems that guarantees fault coverage. The comparison is done using three case studies taken from the automotive and railway domains. The obtained results show that complete ioco is more efficient in detecting deep faults (i.e., the faults reached through longer traces) in large state spaces while ioco is more efficient in detecting shallow faults (i.e., the faults reached through shorter traces) in small state spaces.

Place, publisher, year, edition, pages
Halmstad: Halmstad University Press, 2017. p. 91
Series
Halmstad University Dissertations ; 30
National Category
Embedded Systems
Identifiers
urn:nbn:se:hh:diva-33893 (URN)978-91-87045-62-2 (ISBN)978-91-87045-63-9 (ISBN)
Presentation
2017-05-29, Trade Center, Kristian IV:s väg 3, Halmstad, 10:00 (English)
Opponent
Supervisors
Available from: 2017-07-05 Created: 2017-05-26 Last updated: 2018-03-23Bibliographically approved

Open Access in DiVA

fulltext(711 kB)69 downloads
File information
File name FULLTEXT01.pdfFile size 711 kBChecksum SHA-512
240f063b0ab93bd91d755d4228a70e6e3b036528f75461ae9cd00b57699a7872f34b7fbf715c87a0904cfe4863f0b0a65a37727e30e4b6d0934f0bd7b6fd27dc
Type fulltextMimetype application/pdf

Other links

Publisher's full textScopus

Search in DiVA

By author/editor
Varshosaz, MahsaMousavi, Mohammad Reza
By organisation
Centre for Research on Embedded Systems (CERES)
Computer and Information Sciences

Search outside of DiVA

GoogleGoogle Scholar
Total: 69 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
isbn
urn-nbn

Altmetric score

doi
isbn
urn-nbn
Total: 140 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