Formal Conformance Testing of Systems with Refused Inputs and Forbidden Actions

Burdonov, Igor; Kossatchev, A. S.; Kuliamin, Victor V.

doi:10.1016/j.entcs.2006.09.008

Cited by 16 publications

(17 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Refusals in the presence of inputs have been studied in [11,3,2]. The key difference between these previous approaches and ours is that they allowed refusals to be observed in states where outputs are enabled.…”

Section: Discussionmentioning

confidence: 99%

“…Other lines of work are related to ours in that they investigated refusals for inputs [11,3,2]. These, however, allow refusals to be observed in states from which an output is possible.…”

Section: Introductionmentioning

confidence: 99%

“…In the software testing community, there has been much interest in inputoutput labelled transition systems (IOLTSs) [2], and it is typically assumed that it is possible to observe quiescence, a state in which all enabled events are inputs and it is not possible to take an internal transition. Most approaches use the ioco implementation relation [23]; observations are traces that include inputs, outputs, and quiescence, the only type of refusal that can be observed.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Testing with Inputs and Outputs in CSP

Cavalcanti

Hierons

2013

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. This paper addresses refinement and testing based on CSP models, when we distinguish input and output events. From a testing perspective, there is an asymmetry: the tester (or the environment) controls the inputs, and the system under test controls the outputs. The standard models and refinement relations of CSP are, therefore, not entirely suitable for testing. Here, we adapt the CSP stable-failures model, resulting in the notion of input-output failures refinement. We compare that with the ioco relation often used in testing.Finally, we adapt the CSP testing theory, and show that some tests become unnecessary.

show abstract

Section: Discussionmentioning

confidence: 99%

“…Other lines of work are related to ours in that they investigated refusals for inputs [11,3,2]. These, however, allow refusals to be observed in states from which an output is possible.…”

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Testing with Inputs and Outputs in CSP

Cavalcanti

Hierons

2013

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…These issues have drawn significant attention of the testing community, e.g., [1,6,7,11], and have been dealt with by allowing implicitly or explicitly the presence of channels, e.g., FIFO queues, between the IUT and tester [6,7,17]. However, queues impose a hard burden on the tester, since the communication is now distorted by possible delay in the transmission of messages via queues.…”

Section: Introductionmentioning

confidence: 99%

Generating Complete and Finite Test Suite for ioco: Is It Possible?

Simão

Petrenko

2014

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

Testing from Input/Output Transition Systems has been intensely investigated. The conformance between the implementation and the specification is often determined by the so-called ioco-relation. However, generating tests for ioco is usually hindered by the problem of conflicts between inputs and outputs. Moreover, the generation is mainly based on nondeterministic methods, which may deliver complete test suites but require an unbounded number of executions. In this paper, we investigate whether it is possible to construct a finite test suite which is complete in a predefined fault domain for the classical ioco relation even in the presence of input/output conflicts. We demonstrate that it is possible under certain assumptions about the specification and implementation, by proposing a method for complete test generation, based on a traditional method developed for FSM.

show abstract

“…Usually, it is assumed that the interaction between the tester and an implementation under test (IUT) is synchronous, implicitly assuming that the IUT can either refuse or accept inputs [2] [7] [12]. On the other hand, as the IUT can produce outputs at any moment, the tester should be prepared to accept all outputs from the IUT, or else be able to block (refuse) outputs of the implementation [2].…”

Section: Introductionmentioning

confidence: 99%

From Test Purposes to Asynchronous Test Cases

Simão¹,

Petrenko

2010

2010 Third International Conference on Software Testing, Verification, and Validation Workshops

View full text Add to dashboard Cite

In this paper, we investigate the problem of constructing a test case for a given test purpose and specification modelled by input/output transition systems (IOTS). The communication between the tester and the implementation under test is assumed to be asynchronous, performed via queues. Differently from synchronous tests, when issuing verdicts, asynchronous tests should take into account the distortion caused by the queues in the observed interactions. We propose an algorithm which constructs a sound test case, by transforming the test purpose prior to composing it with the specification without queues, mitigating the state explosion problem which usually occurs when queues are directly involved in the composition. Experimental results confirm the resulting state space reduction. The proposed approach can also be used to obtain sound asynchronous tests from synchronous tests. We identify a class of IOTS specifications for which synchronous and asynchronous tests coincide.

show abstract

Formal Conformance Testing of Systems with Refused Inputs and Forbidden Actions

Cited by 16 publications

References 4 publications

Testing with Inputs and Outputs in CSP

Testing with Inputs and Outputs in CSP

Generating Complete and Finite Test Suite for ioco: Is It Possible?

From Test Purposes to Asynchronous Test Cases

Contact Info

Product

Resources

About