Generating optimal distinguishing sequences with a model checker

Robinson-Mallett, Christopher; Liggesmeyer, Peter; Mücke, Tilo; Goltz, Ursula

doi:10.1145/1082983.1083283

Cited by 10 publications

(10 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…• U-method or unique input/output sequence (UIO) [4,5] • D-method or distinguishing sequence (DS) [5,8] • W-method or characterization set (W-set) [5,6] Let us briefly highlight the essence of these three methods.…”

Section: Conformance Testing Of Finite State Machinesmentioning

confidence: 99%

“…To verify if the implemented machine complies with its requirements, we generate an input for the machine and observe the resulting outputs. With this regard, various testing methods were proposed, say U-method [4,5], Wmethod [5,6], T-method [5,7], and D-method [5,8]. Each of these methods comes with some advantages however there are some limitations.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A hybrid optimization approach to conformance testing of finite automata

Zaniewski

Pedrycz

2014

Applied Soft Computing

View full text Add to dashboard Cite

Section: Conformance Testing Of Finite State Machinesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

A hybrid optimization approach to conformance testing of finite automata

Zaniewski

Pedrycz

2014

Applied Soft Computing

View full text Add to dashboard Cite

“…In (Robinson-Mallett et al 2006b) we adapted these approaches to component black box testing, also referred to as conformance testing (Bochmann and Petrenko 1994), which allows the tester to deduce the intra-component coverage through observation of the interface input/output behavior only. Similarly to (Robinson-Mallett et al 2005) and (Robinson-Mallett et al 2006b) we used CTL for the expression of coverage criteria and complemented the component's behavior specification. Therefore it should be relatively straight-forward to combine both approaches in order to achieve complete test coverage at the inter-and intra-component levels.…”

Section: Related Workmentioning

confidence: 99%

Using communication coverage criteria and partial model generation to assist software integration testing

et al. 2008

Self Cite

View full text Add to dashboard Cite

This paper considers the problem of integration testing the components of a timed distributed software system. We assume that communication between the components is specified using timed interface automata and use computational tree logic (CTL) to define communication-based coverage criteria that refer to send-and receive-statements and communication paths. The proposed method enables testers to focus during component integration on such parts of the specification, e.g. behaviour specifications or Markovian usage models, that are involved in the communication between components to be integrated. A more specific application area of this approach is the integration of test-models, e.g. a transmission gear can be tested based on separated models for the driver behaviour, the engine condition, and the mechanical and hydraulical transmission states. Given such a state-based specification of a distributed system and a concrete coverage goal, a model checker is used in order to determine the coverage or generate test sequences that achieve the goal. Given the generated test sequences we derive a partial test-model of the components from which the test sequences were derived. The partial model can be used to drive further testing and can also be used as the basis for producing additional partial models in incremental integration testing. While the process of deriving the test sequences could suffer from a combinatorial explosion, the effort required to generate the partial model is polynomial in the number of test sequences and their length. Thus, where it is not feasible to produce test sequences that achieve a given type of coverage it is still possible to produce a partial model on the basis of test sequences generated to achieve some other criterion. As a result, the process of generating a partial model has the potential to scale to large industrial software systems. While a particular model checker, UPPAAL, was used, it should be relatively straightforward to adapt the approach for use with other CTL based model checkers. A potential additional benefit of the approach is that it provides a visual description of the state-based testing of distributed systems, which may be beneficial in other contexts such as education and comprehension.

show abstract

“…Connections between test sequence generation and model checking have been considered in some specification based testing literatures [2] [7] [9] [10] [15]. In this paper, we present an approach to find NIO sequences using model checking.…”

Section: Introductionmentioning

confidence: 99%

Finding Narrow Input/Output (NIO) Sequences by Model Checking

Huang

Chung

2008

2008 Sixth International Conference on Software Engineering Research, Management and Applications

View full text Add to dashboard Cite

Conformance test sequences for communication protocols specified by finite state machines (FSM) often use unique input/output (UIO) sequences to detect state transition transfer faults. Since a UIO sequence may not exist for every state of an FSM, in the previous research, we extended UIO sequence to introduce a new concept called narrow input/output (NIO) sequence. The general computation of NIO sequences may lead to state explosion when an FSM is very large. In this paper, we present an approach to find NIO sequences using symbolic model checking. Constructing a Kripke structure and a computation tree logic (CTL) formula for such a purpose is described in detail. We also illustrate the method using a model checker SMV.

show abstract

Generating optimal distinguishing sequences with a model checker

Cited by 10 publications

References 11 publications

A hybrid optimization approach to conformance testing of finite automata

A hybrid optimization approach to conformance testing of finite automata

Using communication coverage criteria and partial model generation to assist software integration testing

Finding Narrow Input/Output (NIO) Sequences by Model Checking

Contact Info

Product

Resources

About