Model-based Testing of Interactive Systems using Interaction Sequences

Turner, Jessica; Bowen, Judy; Reeves, Steve

doi:10.1145/3397873

Cited by 3 publications

(4 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In order to generate tests for Espresso, we must define a process which translates the interaction into test scripts and provides adequate test coverage. To achieve this, we use Interaction Sequence (ISeq) models [13] as the basis for test generation. ISeq models describe user interactions as sequences of actions upon widgets and can be described in text, as finite state automata, or as directed graphs.…”

Section: Modelling Interaction Sequencesmentioning

confidence: 99%

Software Engineering

2024

View full text Add to dashboard Cite

The Espresso capture/replay testing tool for Android applications creates tests that are prone to test fragility, in that when small changes occur to the user interface, tests break and are unable to be re-run. To reduce the fragility and its impact inherent in Espresso tests, we take a modeldriven development approach to test generation. Using interaction sequence models as the basis for generation, we are able to create test scripts that can be run in Android Studio identically to manually recorded tests. This process simplifies scripts when compared with those generated by recording and reduces the time required by developers to create and maintain the test suite, resulting in higher quality testing and validation of Android user interfaces.

show abstract

Section: Modelling Interaction Sequencesmentioning

confidence: 99%

Software Engineering

2024

View full text Add to dashboard Cite

show abstract

“…In contrast, we seek to support usercentred design approaches by providing a way of incorporating light-weight design artefacts into a more formal model-driven approach. As such, we build on approaches which seek to support interaction design in safety-critical domains through the use of combining models at different levels of focus and abstraction (such as [23]- [26] etc.) As has been described previously, the use of different types of models adopted in such approaches leads to a wide-range of benefits over and above the provision of formal descriptions [27] and we envisage these benefits will also be seen for IoT development.…”

Section: A Model-driven Development (Mdd)mentioning

confidence: 99%

“…These cards fall into one of two categories, user experience or system design. For example, "Ethics Cards" 6 and "The Tarot Cards of Tech" 7 , demonstrate ways to use ideation in designing user experience. Alternatively, Karakuri IoT [30] and the Tiles IoT Toolkit Cards [31] are decks used for the ideation of IoT applications.…”

Section: B Informal Design Artefactsmentioning

confidence: 99%

See 1 more Smart Citation

Interaction Modelling for IoT

Turner

Bowen

Zandwijk

2021

2021 28th Asia-Pacific Software Engineering Conference (APSEC)

Self Cite

View full text Add to dashboard Cite

Informal design artefacts allow end-users and nonexperts to contribute to software design ideas and development. In contrast, software engineering techniques such as modeldriven development support experts in ensuring quality properties of the software they propose and build. Each of these approaches have benefits which contribute to the development of robust, reliable and usable software, however it is not always obvious how best to combine these two. In this paper we describe a novel technique which allows us to use informal design artefacts, in the form of ideation card designs, to generate formal models of IoT applications. To implement this technique, we created the Cards-to-Model (C2M) tool which allows us to automate the model generation process. We demonstrate this technique with a case study for a safety-critical IoT application called "Medication Reminders". By generating formal models directly from the design we reduce the complexity of the modelling process. In addition, by incorporating easy-to-use informal design artefacts in the process we allow non-experts to engage in the design and modelling process of IoT applications.

show abstract

Engineering Model-Based Software Testing of WIMP Interactive Applications

Canny

Martinie

Navarre

et al. 2021

Proc. ACM Hum.-Comput. Interact.

View full text Add to dashboard Cite

The goal of software testing is to detect defects with the objective of removing them at a later stage in the development process. Interactive software development follows the User Centered Design approach that promotes continuous involvement of users both at design and evaluation phases. This process is meant to produce usable interactive software by gathering functional and non-functional requirements related to both user needs and context of use. However, taking into account these potentially very-complex-to-implement requirements increases the complexity of the software that is likely, without appropriate methods and tools, to encompass a large number of defects. One of the limitations of UCD approaches is that it provides no guidance on the engineering of the interactive application, which thus usually embeds numerous defects resulting in failures at the origin of user frustrations and performance drops. Even though a classification of interactive application defects has been proposed, interactive application testers remain only superficially supported in detecting them. This paper defines a model-based approach to engineer the testing activity for interactive applications. It proposes a process that bridges the gap between UCD artefacts and interactive software implementation by the production of a dedicated formal model exploited for testing purposes only. The application of the process is demonstrated on an interactive cockpit WIMP application. Finally, threats to validity (capability of the approach to detect defects and to ensure an acceptable coverage testing of the interactive application) are addressed by a longitudinal study on 61 variants of a simple application developed by 61 different developers. ?

show abstract

Model-based Testing of Interactive Systems using Interaction Sequences

Cited by 3 publications

References 24 publications

Software Engineering

Software Engineering

Interaction Modelling for IoT

Engineering Model-Based Software Testing of WIMP Interactive Applications

Contact Info

Product

Resources

About