Model-Based Testing for Asynchronous Systems

Graf-Brill, Alexander; Hermanns, Holger

doi:10.1007/978-3-319-67113-0_5

Cited by 7 publications

(4 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Most of the previous publications give new MBT approaches. For example Graf-Brill and Hermanns (2017), have proposed an approach that use model-based testing to test asynchronous communicating systems. Also, Wang et al (2017) used model based testing to validate quorum-based systems implemented using the Gorums library through a new approach.…”

Section: Discussionmentioning

confidence: 99%

Combining Model-Based Testing and Failure Modes and Effects Analysis for Test Case Prioritization: A Software Testing Approach

Meriem¹,

Abdelaziz²

2019

Journal of Computer Science

View full text Add to dashboard Cite

Due to The complexity of modern software projects and the increasing size of software systems, it becomes difficult to manually perform tests with limited resources. Also, manual testing cannot assure that the software is tested using all possible combinations of inputs. Therefore, automate software testing activities have become primordial in the Software Development Life Cycle (SDLC). Model-based testing is a prominent validation technique in software testing that uses models of the system under test to automatically generate test cases; this generation leads to a large number of test cases; which cannot exhaustively be executed, due to time and cost constraints. Moreover, the test-cases execution order has an influence on the rate at which faults can be detected. Therefore, it is essential to prioritize test cases in order to execute the most important with limited time and cost. On the other hand, The Failure Mode and Effects Analysis (FMEA) considered as one of the formal techniques to do risk based testing. It offers a structured methodology to identifying the system failure modes, analyzing their effects and setting up controls to risk reducing and improve the quality of systems or products. By applying such a technique to Model-based testing projects, we can benefit from FMEA analysis and the automating in same project. Through this paper, we introduced a new model based testing approach for prioritizing and ranking test cases according to the requirements and failure modes. In the suggested approach we used the Failure Mode and Effect Analysis methodology in model based testing way to automatically generate a set of pair {test case, priority number} to prioritize test cases. It differs from existing approaches in that it generates two types of test cases; requirement-based test cases and failure mode-based test cases. For the purpose of experimental evaluation and analysis, we will compare the suggested approach with some well-known prioritization methods and we will present a case study to illustrate the potential application of the proposed approach in a future work.

show abstract

Section: Discussionmentioning

confidence: 99%

Combining Model-Based Testing and Failure Modes and Effects Analysis for Test Case Prioritization: A Software Testing Approach

Meriem¹,

Abdelaziz²

2019

Journal of Computer Science

View full text Add to dashboard Cite

show abstract

“…The reduction removes all internal transitions (created by the hiding), so that all actions of CTG C are either an input or an output of C. A precondition for a successful projection is that all inputs and outputs of C, as well as the verdict transitions, are present and visible in CTG. Notice that projecting onto the interface of C enables synchronous interaction between the tester and an SUT of C, avoiding all issues related to the asynchronous communication [32,13] present in the GALS model.…”

Section: Test Graph Projectionmentioning

confidence: 99%

Asynchronous Testing of Synchronous Components in GALS Systems

Marsso

Mateescu

Parissis

et al. 2019

Lecture Notes in Computer Science

View full text Add to dashboard 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.

show abstract

“…Application context EnergyBus. The EnergyBus is a case study [5] which drives the concrete development of model-based testing theory and applications of us and our coworkers [15,13,14,20]. It aims at establishing a common basis for the interchange and interoperation of electric devices in the context of energy management systems (EMS).…”

Section: A Practical Theorymentioning

confidence: 99%

Component-aware Input-Output Conformance

Graf-Brill

Hermanns

2019

Formal Techniques for Distributed Objects, Components, and Systems

Self Cite

View full text Add to dashboard Cite

Black-box conformance testing based on a compositional model of the intended behaviour is a very attractive approach to validate the correctness of an implementation. In this context, input-output conformance is a scientifically well-established formalisation of the testing process. This paper discusses peculiar problems arising in situations where the implementation is a monolithic black box, for instance for reasons of intellectual property restrictions, while the specification is compositional. In essence, tests need to be enabled to observe progress in individual specification-level components. For that, we will reconsider input-output conformance so that it can faithfully deal with such situations. Refined notions of quiescence play a central role in a proper treatment of the problem. We focus on the scenario of parallel components with fully asynchronous communication covering very many notorious practical examples. We finally illustrate the practical implications of component-aware conformance testing in the context of a prominent example, namely networked embedded software.

show abstract

Model-Based Testing for Asynchronous Systems

Cited by 7 publications

References 19 publications

Combining Model-Based Testing and Failure Modes and Effects Analysis for Test Case Prioritization: A Software Testing Approach

Combining Model-Based Testing and Failure Modes and Effects Analysis for Test Case Prioritization: A Software Testing Approach

Asynchronous Testing of Synchronous Components in GALS Systems

Component-aware Input-Output Conformance

Contact Info

Product

Resources

About