Formal Modeling of Testing Software for Cyber-Physical Automation Systems

Buzhinsky, Igor; Pang, Cheng; Vyatkin, Valeriy

doi:10.1109/trustcom.2015.648

Cited by 12 publications

(18 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This work continues the research direction established in [6], where a testing framework based of the net condition/event systems (NCES) [7] formalism has been proposed. Unlike [6], the approach presented in this paper is generic with respect to the employed formal language. In particular, we apply it together with wide-spread model checking environments SPIN 1 and NuSMV 2 .…”

Section: Introductionmentioning

confidence: 60%

Section: Related Workmentioning

confidence: 99%

“…This paper is a direct continuation of the work [6], where a framework for formal modeling of the testing process for automation systems is proposed. In [6], testing is modeled using the formalism of NCES. While the basic idea of [6] is similar to the one of the present paper, the latter develops the former in two aspects: in terms of supported model languages (the ones with better tool support are used) and by considering a more general test case representation.…”

Section: Related Workmentioning

confidence: 99%

“…Test suites are represented as trees. A similar representation of test cases is employed in [6], except that inputs and output are now separated.…”

Section: A Formal Test Case Representationsmentioning

confidence: 99%

“…• Test case models judge whether the controller's behavior is correct or not. The simplest type of models which submits to these requirements is the linear sequence of inputs and required outputs, like the one in [6]. However, such models require concrete behavior from the controller for each input scenario and An example of a test case model visually represented as an FSM is shown in Fig.…”

Section: Test Case Modelingmentioning

confidence: 99%

See 4 more Smart Citations

Testing automation systems by means of model checking

Buzhinsky

Vyatkin

2017

2017 22nd IEEE International Conference on Emerging Technologies and Factory Automation (ETFA)

Self Cite

View full text Add to dashboard Cite

Industrial automation systems are commonly obliged to comply with correctness requirements and safety standards. Testing and simulation are traditionally used to ensure this compliance. For mission-critical applications, formal verification and model checking in particular are also used, but such techniques are computationally intensive and difficult to apply in practice. This paper searches for synergies between testing and model checking by generalizing an earlier proposed formal test modeling framework. It presents a technique of testing automation systems with the use of model checking, which now supports multiple model checking environments and a more generic test case representation. The proposed technique is applied on a case study involving a simple safety-critical system with timing requirements. Experiments show that the technique is fast despite the use of formal methods and at the same time has several benefits compared to usual testing.

show abstract

Section: Introductionmentioning

confidence: 60%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

“…Test suites are represented as trees. A similar representation of test cases is employed in [6], except that inputs and output are now separated.…”

Section: A Formal Test Case Representationsmentioning

confidence: 99%

Section: Test Case Modelingmentioning

confidence: 99%

See 3 more Smart Citations

Testing automation systems by means of model checking

Buzhinsky

Vyatkin

2017

2017 22nd IEEE International Conference on Emerging Technologies and Factory Automation (ETFA)

Self Cite

View full text Add to dashboard Cite

show abstract

Root causing, detecting, and fixing flaky tests: State of the art and future roadmap

et al. 2020

View full text Add to dashboard Cite

A flaky test is a test that may lead to different results in different runs on a single code under test without any change in the test code. Test flakiness is a noxious phenomenon that slows down software deployment, and increases the expenditures in a broad spectrum of platforms such as software‐defined networks and Internet of Things environments. Industrial institutes and labs have conducted a whole lot of research projects aiming at tackling this problem. Although this issue has been receiving more attention from academia in recent years, the academic research community is still behind the industry in this area. A systematic review and trend analysis on the existing approaches for detecting and root causing flaky tests can pave the way for future research on this topic. This can help academia keep pace with industrial advancements and even lead the research in this field. This article first presents a comprehensive review of recent achievements of the industry as well as academia regarding the detection and mitigation of flaky tests. In the next step, recent trends in this line of research are analyzed and a roadmap is established for future research.

show abstract