Test descriptions with ETSI TDL

Makedonski, Philip; Adamis, Gusztáv; Käärik, Martti; Kristoffersen, Finn; Carignani, Michele; Ulrich, Andreas; Grabowski, Jens

doi:10.1007/s11219-018-9423-9

Cited by 13 publications

(10 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In addition, it does not support real-time models, other testing scales such as API testing, and distributed test execution since the testing DSL that is used, involves only basic testing elements while there are other testing DSLs covering those of complex. For example, Test Description Language (TDL) is a DSL for high-level test specification that is defined to smooth the transition from system requirements to executable test cases written in TTCN-3; it is itself a test-specific DSL for black-box testing of distributed systems [17].…”

Section: The Role Of Citizen Developer In Testingmentioning

confidence: 99%

Challenges & opportunities in low-code testing

Khorram

Mottu

Sunyé

2020

Proceedings of the 23rd ACM/IEEE International Conference on Model Driven Engineering Languages and Systems: Companion Proceedi

View full text Add to dashboard Cite

Low-code is a growing development approach supported by many platforms. It fills the gap between business and IT by supporting the active involvement of non-technical domain experts, named Citizen Developer, in the application development lifecycle.Low-code introduces new concepts and characteristics. However, it is not investigated yet in academic research to point out the existing challenges and opportunities when testing low-code software. This shortage of resources motivates this research to provide an explicit definition to this area that we call it Low-Code Testing.In this paper, we initially conduct an analysis of the testing components of five commercial Low-Code Development Platforms (LCDP) to present low-code testing advancements from a business point of view. Based on the low-code principles as well as the result of our analysis, we propose a feature list for low-code testing along with possible values for them. This feature list can be used as a baseline for comparing low-code testing components and as a guideline for building new ones. Accordingly, we specify the status of the testing components of investigated LCDPs based on the proposed features. Finally, the challenges of low-code testing are introduced considering three concerns: the role of citizen developer in testing, the need for high-level test automation, and cloud testing. We provide references to the state-of-the-art to specify the difficulties and opportunities from an academic perspective. The results of this research can be used as a starting point for future research in low-code testing area. CCS CONCEPTS• Software and its engineering → Software testing and debugging.

show abstract

Section: The Role Of Citizen Developer In Testingmentioning

confidence: 99%

Challenges & opportunities in low-code testing

Khorram

Mottu

Sunyé

2020

Proceedings of the 23rd ACM/IEEE International Conference on Model Driven Engineering Languages and Systems: Companion Proceedi

View full text Add to dashboard Cite

show abstract

“…A recent effort of the European Telecommunications Standards Institute (ETSI) led to the creation of the Test Description Language (TDL), a standardized language for the specification of test descriptions (Makedonski et al 2019). Since TDL is not specific to any specific GPL or xDSL, it represents an interesting candidate for generically writing test cases for executable models.…”

Section: Introductionmentioning

confidence: 99%

Adapting TDL to Provide Testing Support for Executable DSLs.

Khorram¹,

Bousse²,

Mottu³

et al. 2021

JOT

View full text Add to dashboard Cite

Testing is one of the most prevalent and successful verification and validation (V&V) techniques used in the field of software engineering. While a large number of testing frameworks exist for general-purpose programming languages, providing testing facilities for any given executable Domain Specific Language (xDSL) remains a costly and challenging task. In this context, a standard such as the Test Description Language (TDL) appears as a suitable foundation for the definition of a generic testing approach for xDSLs. Unfortunately, TDL does not provide the domain-specific concepts required to write test cases for a given xDSL and does not include any model execution facilities. Our contribution addresses these limitations and thereby provides a fully generic testing approach for xDSLs based on TDL. Required TDL domain-specific concepts are automatically inferred from the xDSL definition through a model transformation into TDL. Model execution facilities are provided through the definition of a refined operational semantics for TDL. The application of our approach on 5 different xDSLs shows its generality and that it can successfully be used for testing executable models.

show abstract

“…Concrete test scripting languages, such as TTCN-3, regardless their strict semantics are not well suited for high-level description of test scenarios. They rather follow the style of syntax typical to imperative programming languages [12].…”

Section: Introductionmentioning

confidence: 99%

“…Without formal semantics the development of test descriptions by means of different notations and dialects led to overhead and inconsistencies that need to be checked and fixed manually. As a consequence, ETSI started a new initiative by developing the Test Description Language TDL [12]. It is intended to bridge the gap between declarative test purposes and imperative test cases by offering a standardized approach for the specification of test descriptions.…”

Section: Introductionmentioning

confidence: 99%

“…It is intended to bridge the gap between declarative test purposes and imperative test cases by offering a standardized approach for the specification of test descriptions. The main benefits of ETSI TDL outlined in [12] are higher quality tests through better design, easier layout to review by non-testing experts, better and faster test development, and seamless integration of methodology and tools.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Test Scenario Specification Language for Model-Based Testing

Halling¹,

Vain²,

Boyarchuk³

et al. 2019

IJC

View full text Add to dashboard Cite

In mission critical systems a single failure might cause catastrophic consequences. This sets high expectations to timely detection of design faults and runtime failures. By traditional software testing methods the detection of deeply nested faults that occur sporadically is almost impossible. The discovery of such bugs can be facilitated by generating well-targeted test cases where the test scenario is explicitly specified. On the other hand, the excess of implementation details in manually crafted test scripts makes it hard to understand and to interpret the test results. This paper defines high-level test scenario specification language TDLTP for specifying complex test scenarios that are relevant for model-based testing of mission critical systems. The syntax and semantics of TDLTP operators are defined and the transformation rules that map its declarative expressions to executable Uppaal Timed Automata test models are specified. The scalability of the method is demonstrated on the TUT100 satellite software integration testing case study.

show abstract

Test descriptions with ETSI TDL

Cited by 13 publications

References 7 publications

Challenges & opportunities in low-code testing

Challenges & opportunities in low-code testing

Adapting TDL to Provide Testing Support for Executable DSLs.

Test Scenario Specification Language for Model-Based Testing

Contact Info

Product

Resources

About