From LOTOS to LNT

Lecture Notes in Computer Science

Parissis

et al. 2019

Self Cite

GALS (Globally Asynchronous Locally Synchronous) systems, such as the Internet of Things or autonomous cars, integrate reactive synchronous components that interact asynchronously. The complexity induced by combining synchronous and asynchronous aspects makes GALS systems difficult to develop and debug. Ensuring their functional correctness and reliability requires rigorous design methodologies, based on formal methods and assisted by validation tools. In this paper we propose a testing methodology for GALS systems integrating: (1) synchronous and asynchronous concurrent models; (2) functional unit testing and behavioral conformance testing; and (3) various formal methods and their tool equipments. We leverage the conformance test generation for asynchronous systems to automatically derive realistic scenarios (input constraints and oracle), which are necessary ingredients for the unit testing of individual synchronous components, and are difficult and error-prone to design manually. We illustrate our approach on a simple, but relevant example inspired by autonomous cars.

Section: Model Checking and Conformance Test Generationmentioning

confidence: 99%

Asynchronous Testing of Synchronous Components in GALS Systems

Lecture Notes in Computer Science

Parissis

et al. 2019

Self Cite

“…Using the LNT language [8,17], one would be tempted to write this TP as the process PURPOSE1, simply containing the desired sequence of three inputs (on gates CRYPT, KEY, and DATA) followed by an output (on gate OUTPUT): Following the conventions of TGV, we mark accepting (respectively, refusal) states by a self-loop labeled with T_ACCEPT (respectively, T_REFUSE).…”

Section: Examples Of Different Ways To Express a Test Purposementioning

confidence: 99%

TESTOR: A Modular Tool for On-the-Fly Conformance Test Case Generation

Lecture Notes in Computer Science

Serwe

2018

Self Cite

Abstract. We present TESTOR, a tool for on-the-fly conformance test case generation, guided by test purposes. Concretely, given a formal specification of a system and a test purpose, TESTOR automatically generates test cases, which assess using black box testing techniques the conformance to the specification of a system under test. In this context, a test purpose describes the goal states to be reached by the test and enables one to indicate parts of the specification that should be ignored during the testing process. Compared to the existing tool TGV, TESTOR has a more modular architecture, based on generic graph transformation components, is capable of extracting a test case completely on the fly, and enables a more flexible expression of test purposes, taking advantage of the multiway rendezvous. TESTOR has been implemented on top of the CADP verification toolbox, evaluated on three published case-studies and more than 10000 examples taken from the non-regression test suites of CADP.

“…Taking the draft specification of the Transport Layer security (TLS) [13] protocol Version 1.3 as starting point, our main contribution in this paper is the formalisation of the Handshake protocol of TLS in the LNT language [12,7]. In this section, we give a brief description of our model, which encompasses the handshake messages and illustrate then the handshake interactions.…”

Section: Formal Model Of the Tls Handshake In Lntmentioning

confidence: 99%

A Formal TLS Handshake Model in LNT

Božić

Electron. Proc. Theor. Comput. Sci.

et al. 2018

Testing of network services represents one of the biggest challenges in cyber security. Because new vulnerabilities are detected on a regular basis, more research is needed. These faults have their roots in the software development cycle or because of intrinsic leaks in the system specification. Conformance testing checks whether a system behaves according to its specification. Here model-based testing provides several methods for automated detection of shortcomings. The formal specification of a system behavior represents the starting point of the testing process. In this paper, a widely used cryptographic protocol is specified and tested for conformance with a test execution framework. The first empirical results are presented and discussed.