Model-based testing of software and systems: recent advances and challenges

Petrenko, Alexandre; Simão, Adenilso da Silva; Maldonado, José Carlos

doi:10.1007/s10009-012-0240-3

Cited by 26 publications

(10 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Di®ering from these works, Petrenko et al stated in 2012 that a long-term challenge in test generation is related to the data aspect of test models [42]. One recent work proposed reducing test length for FSMs with extra states [51].…”

Section: Related Workmentioning

confidence: 98%

“…One type of holistic models is sequential models, which include¯nite state machines (FSMs), input/output transition systems (IOTSs), and various state machines [42]. Our work follows FSM-based GUI testing that is explained in the following before we compare it with other, theoretically sound approaches.…”

Section: Theoretical Backgroundmentioning

confidence: 99%

“…Two main types of models considered in this testing context are holistic models and scenario models, where the former are models which attempt to describe the expected behavior of a system under consideration (SUC) as completely as possible in a single formal speci¯cation, while the latter focus on a number of test scenarios describing various aspects of the expected behavior [42].…”

Section: Theoretical Backgroundmentioning

confidence: 99%

See 2 more Smart Citations

Input Contract Testing of Graphical User Interfaces

Tuğlular

Belli

Linschulte³

2016

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

User inputs are critical for the security, safety, and reliability of software systems. This paper proposes a new concept called user input contracts, which is an integral part of a design-bycontract supplemented development process, and a model-based testing approach to detect violations of user input contracts. The approach generates test cases from an input contract integrated with graph-based model of user interface speci¯cation and applies them to the system under consideration. The paper presents a proof-of-concept tool that has been developed and used to validate the approach by experiments. The experiments are conducted on a web-based system for marketing tourist services to analyze input robustness of system under consideration with respect to user input contracts.

show abstract

Section: Related Workmentioning

confidence: 98%

Section: Theoretical Backgroundmentioning

confidence: 99%

Section: Theoretical Backgroundmentioning

confidence: 99%

See 1 more Smart Citation

Input Contract Testing of Graphical User Interfaces

Tuğlular

Belli

Linschulte³

2016

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

show abstract

“…The investigation of complete testing methods is a very active research field [23]. The H-Method [6] applied for testing in this paper has been selected because (1) it produces far less test cases than the "classical" W-Method [5], but (2) it is still very intuitive with regard to the test case selection principles.…”

Section: Introductionmentioning

confidence: 99%

Complete Test of Synthesised Safety Supervisors for Robots and Autonomous Systems

Gleirscher

Peleskã

2021

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

Verified controller synthesis uses world models that comprise all potential behaviours of humans, robots, further equipment, and the controller to be synthesised. A world model enables quantitative risk assessment, for example, by stochastic model checking. Such a model describes a range of controller behaviours some of which-when implemented correctly-guarantee that the overall risk in the actual world is acceptable, provided that the stochastic assumptions have been made to the safe side. Synthesis then selects an acceptable-risk controller behaviour. However, because of crossing abstraction, formalism, and tool boundaries, verified synthesis for robots and autonomous systems has to be accompanied by rigorous testing. In general, standards and regulations for safety-critical systems require testing as a key element to obtain certification credit before entry into service. This work-in-progress paper presents an approach to the complete testing of synthesised supervisory controllers that enforce safety properties in domains such as human-robot collaboration and autonomous driving. Controller code is generated from the selected controller behaviour. The code generator, however, is hard, if not infeasible, to verify in a formal and comprehensive way. Instead, utilising testing, an abstract test reference is generated, a symbolic finite state machine with simpler semantics than code semantics. From this reference, a complete test suite is derived and applied to demonstrate the observational equivalence between the synthesised abstract test reference and the generated concrete controller code running on a control system platform.

show abstract

“…These methods restrict the input space using static analysis and apply (non-uniform) random test case generation. Modelbased testing (see [28,29] for surveys on this topic) considers specification models based on labelled transition systems. For instance, extended finite state machines (EFSM) [30][31][32] are commonly used in communication protocol testing to provide exhaustive test case generation for conformance testing.…”

Section: Related Workmentioning

confidence: 99%

Generating test case chains for reactive systems

Schrammel

Melham

Kroening

2014

Int J Softw Tools Technol Transfer

View full text Add to dashboard Cite

Testing of reactive systems is challenging because long input sequences are often needed to drive them into a state to test a desired feature. This is particularly problematic in on-target testing, where a system is tested in its real-life application environment and the amount of time required for resetting is high. This article presents an approach to discovering a test case chain-a single software execution that covers a group of test goals and minimizes overall test execution time. Our technique targets the scenario in which test goals for the requirements are given as safety properties. We give conditions for the existence and minimality of a single test case chain and minimize the number of test case chains if a single test case chain is infeasible. We report experimental results with our ChainCover tool for C code generated from Simulink models and compare it to state-of-the-art test suite generators.

show abstract

Model-based testing of software and systems: recent advances and challenges

Cited by 26 publications

References 29 publications

Input Contract Testing of Graphical User Interfaces

Input Contract Testing of Graphical User Interfaces

Complete Test of Synthesised Safety Supervisors for Robots and Autonomous Systems

Generating test case chains for reactive systems

Contact Info

Product

Resources

About