An introduction to the testing and test control notation (TTCN-3)

Grabowski, Jens; Hogrefe, Dieter; Réthy, György; Schieferdecker, Ina; Wiles, Anthony; Willcock, Colin

doi:10.1016/s1389-1286(03)00249-4

Cited by 100 publications

(40 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To make use of existing test frameworks the Testing and Test Control Notation Version 3 (TTCN3) was selected because of its long history of usage for telecommunication protocols [2] and as a tool officially selected for 6LoWPAN plugtests driven by the European Telecommunications Standards Institute (ETSI).…”

Section: Ipv6 For Dect Ule Networkmentioning

confidence: 99%

“…This holds true for the functional testing as well as for interoperability testing. Nevertheless with the Testing and Test Control Notation version 3 (TTCN-3) a scripting language and specification exists that is commonly known and used in conformance testing of communicating systems [2]. With the help of so-called TTCN-3 compilers such as Titan TTCN-3, the target system's performance can be evaluated and, moreover, the resulting test system can verify the system under test's conformity with respective to standards or the interoperability with other implementations.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Titan TTCN-3 Based Test Framework for Resource Constrained Systems

2016

View full text Add to dashboard Cite

Abstract. Wireless communication systems more and more become part of our daily live. Especially with the Internet of Things (IoT) the overall connectivity increases rapidly since everyday objects become part of the global network. For this purpose several new wireless protocols have arisen, whereas 6LoWPAN (IPv6 over Low power Wireless Personal Area Networks) can be seen as one of the most important protocols within this sector. Originally designed on top of the IEEE802.15.4 standard it is a subject to various adaptions that will allow to use 6LoWPAN over different technologies; e.g. DECT Ultra Low Energy (ULE). Although this high connectivity offers a lot of new possibilities, there are several requirements and pitfalls coming along with such new systems. With an increasing number of connected devices the interoperability between different providers is one of the biggest challenges, which makes it necessary to verify the functionality and stability of the devices and the network. Therefore testing becomes one of the key components that decides on success or failure of such a system. Although there are several protocol implementations commonly available; e.g., for IoT based systems, there is still a lack of according tools and environments as well as for functional and conformance testing. This article describes the architecture and functioning of the proposed test framework based on Testing and Test Control Notation Version 3 (TTCN-3) for 6LoWPAN over ULE networks.

show abstract

Section: Ipv6 For Dect Ule Networkmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Titan TTCN-3 Based Test Framework for Resource Constrained Systems

2016

View full text Add to dashboard Cite

show abstract

“…A broad variety of formal or informal models exist for modeling software as recommended in standards such as UML [1] or TTCN-3 [2]. These models describe the SUC at different levels of granularity and preciseness.…”

Section: Introductionmentioning

confidence: 99%

Model-based mutation testing—Approach and case studies

Belli

Budnik

Hollmann³

et al. 2016

Science of Computer Programming

View full text Add to dashboard Cite

This paper rigorously introduces the concept of model-based mutation testing (MBMT) and positions it in the landscape of mutation testing. Two elementary mutation operators, insertion and omission, are exemplarily applied to a hierarchy of graph-based models of increasing expressive power including directed graphs, event sequence graphs, finite-state machines and statecharts. Test cases generated based on the mutated models (mutants) are used to determine not only whether each mutant can be killed but also whether there are any faults in the corresponding system under consideration (SUC) developed based on the original model. Novelties of our approach are: (1) evaluation of the fault detection capability (in terms of revealing faults in the SUC) of test sets generated based on the mutated models, and (2) superseding of the great variety of existing mutation operators by iterations and combinations of the two proposed elementary operators. Three case studies were conducted on industrial and commercial real-life systems to demonstrate the feasibility of using the proposed MBMT approach in detecting faults in SUC, and to analyze its characteristic features. Our experimental data suggest that test sets generated based on the mutated models created by insertion operators are more effective in revealing faults in SUC than those generated by omission operators. Worth noting is that test sets following the MBMT approach were able to detect faults in the systems that were tested by manufacturers and independent testing organizations before they were released.

show abstract

“…In this paper, we discuss another critical issue in conformance testing with MSCs: the Oracle Problem. Both the controllability problem and the Oracle Problem need to be addressed in testing a 1 TTCN was initially an acronym for Tree and Tabular Combined Notation [10] and later for Testing and Test Control Notation [11]. distributed system.…”

Section: Introductionmentioning

confidence: 99%

The Oracle Problem When Testing from MSCs

Dan

Hierons

2013

The Computer Journal

View full text Add to dashboard Cite

Message Sequence Charts (MSCs) form a popular language in which scenariobased specifications and models can be written. There has been significant interest in automating aspects of testing from MSCs. This paper concerns the Oracle Problem, in which we have an observation made in testing and wish to know whether this is consistent with the specification. We assume that there is an MSC specification and consider the case where we have entirely independent local testers (local observability) and where the observations of the local testers are logged and brought together (tester observability). It transpires that under local observability the Oracle Problem can be solved in low-order polynomial time if we use sequencing, loops and choices but becomes NP-complete if we also allow parallel components; if we place a bound on the number of parallel components then it again can be solved in polynomial time. For tester observability, the problem is NP-complete when we have either loops or choices. However, it can be solved in low-order polynomial time if we have only one loop, no choices, and no parallel components. If we allow parallel components then the Oracle Problem is NP-complete for tester observability even if we restrict to the case where there are at most two processes.

show abstract

An introduction to the testing and test control notation (TTCN-3)

Cited by 100 publications

References 10 publications

Titan TTCN-3 Based Test Framework for Resource Constrained Systems

Titan TTCN-3 Based Test Framework for Resource Constrained Systems

Model-based mutation testing—Approach and case studies

The Oracle Problem When Testing from MSCs

Contact Info

Product

Resources

About