A passive testing approach based on invariants: application to the WAP

A survey on formal active and passive testing with applications to the cloud

“…the observation of the system traces without interfering with the system's normal operation [8,3]. Monitoring is also close to run time verification [46].…”

“…In order to do so, a simple adaptation of the classical algorithms for pattern matching on strings was implemented. This work was extended [8] to study a new type of invariants (obligation), to present a tool that implements the approach and to give a complete case study on the Wireless Application Protocol. It is worth pointing out that this protocol represents a typical example where active testing cannot be applied because, in general, there is no direct access to the interfaces between the different layers.…”

“…This approach paved the way for another work by the authors of [39] to extend the simple and obligation invariant to match the EFSM formalism. In [8] the authors assume that the current states of the observed trace are known. In [58] these assumptions are not required.…”

Analysis of the OLSR Protocol by Using Formal Passive Testing

“…Passive testing consists in analyzing the traces recorded from the IUT and trying to find a fault by comparing these traces with either the complete specification or with some specific requirements (see, for example, [7], [8], [9], [10], [11]). A new methodology to perform passive testing was presented in [12], [13], [14]. The main novelty is that a set of invariants is used to represent the most relevant properties of a system.…”

“…Taking as initial step [14], the approach presented in [25], [26] included the possibility of adding time constraints as properties that traces extracted from the IUT must hold. Even though this framework was very appropriate to analyze a large variety of timed systems, we observed that our invariants become large and complicated when there is a big number of nodes in the environment.…”