From Scenarios to Test Implementations Via Promela

Ulrich, Andreas; Alikacem, E.; Hallal, H.; Boroday, Sergiy

doi:10.1007/978-3-642-16573-3_17

Cited by 5 publications

(5 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We focus our research work on a scenario-based approach (instead of state-based testing), because scenario-based models are more convenient for describing and visualizing the interactions that occur between the components and actors of a distributed system in key scenarios [2] [19]. Scenario-based models also help partially avoiding the test case explosion problem.…”

Section: A Model-based Testingmentioning

confidence: 99%

Towards Decentralized Conformance Checking in Model-Based Testing of Distributed Systems

Lima

Faria

2017

2017 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW)

View full text Add to dashboard Cite

In a growing number of domains, the provisioning of end-to-end services to the users depends on the proper interoperation of multiple products, forming a new distributed system. To ensure interoperability and the integrity of this new distributed system, it is important to conduct integration tests that verify not only the interactions with the environment but also the interactions between the system components. Integration test scenarios for that purpose may be conveniently specified by means of UML sequence diagrams, possibly allowing multiple execution paths. The automation of such integration tests requires that test components are also distributed, with a local tester deployed close to each system component, and a central tester coordinating the local testers. In such a test architecture, it is important to minimize the communication overhead during test execution. Hence, in this paper we investigate conditions upon which conformance errors can be detected locally (local observability) and test inputs can be decided locally (local controllability) by the local testers, without the need for exchanging coordination messages between the test components during test execution. The conditions are specified in a formal specification language that allows executing and validating the specification. Examples of test scenarios are also presented, illustrating local observability and controllability problems associated with optional messages without corresponding acknowledgment messages, races and nonlocal choices.

show abstract

Section: A Model-based Testingmentioning

confidence: 99%

Towards Decentralized Conformance Checking in Model-Based Testing of Distributed Systems

Lima

Faria

2017

2017 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW)

View full text Add to dashboard Cite

show abstract

“…Listing 2 shows our scenario-test example (again, semantically equivalent to Listing 1 and Fig. 1) including a precondition (line 6), an event (lines [8][9][10], and an expected outcome (line 11). Epsilon shares similarities with OCL [23].…”

Section: E-notationmentioning

confidence: 99%

“…In MDD, scenario specifications can be used to test models for compliance with corresponding domain requirements (see, e.g., [3], [4], [8]). Different approaches have been proposed to provide notations for specifying scenarios, for example in a table-based layout, as message sequence charts, or via formal methods (see, e.g., [7], [9], [10]). However, no generally accepted standard notation exists and the different scenario notations vary with respect to the corresponding application domain and with the professional background of the stakeholder involved in a particular development project (see, e.g., [7]).…”

Section: Introductionmentioning

confidence: 99%

Comparing Three Notations for Defining Scenario-Based Model Tests: A Controlled Experiment

Hoisl

Sobernig

Strembeck

2014

2014 9th International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

Abstract-Scenarios are an established means to specify requirements for software systems. Scenario-based tests allow for validating software models against such requirements. In this paper, we consider three alternative notations to define such scenario tests on structural models: a semi-structured natural-language notation, a diagrammatic notation, and a fully-structured textual notation. In particular, we performed a study to understand how these three notations compare to each other with respect to accuracy and effort of comprehending scenario-test definitions, as well as with respect to the detection of errors in the models under test. 20 software professionals (software engineers, testers, researchers) participated in a controlled experiment based on six different comprehension and maintenance tasks. For each of these tasks, questions on a scenario-test definition and on a model under test had to be answered. In an ex-post questionnaire, the participants rated each notation on a number of dimensions (e.g., practicality or scalability). Our results show that the choice of a specific scenario-test notation can affect the productivity (in terms of correctness and time-effort) when testing software models for requirements conformance. In particular, the participants of our study spent comparatively less time and completed the tasks more accurately when using the natural-language notation compared to the other two notations. Moreover, the participants of our study explicitly expressed their preference for the natural-language notation.

show abstract

“…The second scenario-test notation is based on UML sequence diagrams [20]. It is inspired by related modelbased scenario-test approaches (see, e.g., [9], [21]). Fig.…”

Section: D-notationmentioning

confidence: 99%

Comparing Three Notations for Defining Scenario-based Model Tests: A Controlled Experiment

Hoisl¹,

Sobernig²,

Strembeck³

2014

2014 9th International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

Scenarios are an established means to specify requirements for software systems. Scenario-based tests allow for validating software models against such requirements. In this paper, we consider three alternative notations to define such scenario tests on structural models: a semi-structured natural-language notation, a diagrammatic notation, and a fully-structured textual notation. In particular, we performed a study to understand how these three notations compare to each other with respect to accuracy and effort of comprehending scenario-test definitions, as well as with respect to the detection of errors in the models under test. 20 software professionals (software engineers, testers, researchers) participated in a controlled experiment based on six different comprehension and maintenance tasks. For each of these tasks, questions on a scenario-test definition and on a model under test had to be answered. In an ex-post questionnaire, the participants rated each notation on a number of dimensions (e.g., practicality or scalability). Our results show that the choice of a specific scenario-test notation can affect the productivity (in terms of correctness and time-effort) when testing software models for requirements conformance. In particular, the participants of our study spent comparatively less time and completed the tasks more accurately when using the natural-language notation compared to the other two notations. Moreover, the participants of our study explicitly expressed their preference for the natural-language notation.

show abstract

From Scenarios to Test Implementations Via Promela

Cited by 5 publications

References 9 publications

Towards Decentralized Conformance Checking in Model-Based Testing of Distributed Systems

Towards Decentralized Conformance Checking in Model-Based Testing of Distributed Systems

Comparing Three Notations for Defining Scenario-Based Model Tests: A Controlled Experiment

Comparing Three Notations for Defining Scenario-based Model Tests: A Controlled Experiment

Contact Info

Product

Resources

About