Software Testing: According to Plan!

Josip Bozic, Franz Wotawa

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Automated planning and scheduling represents a branch of classical artificial intelligence (AI) research. Although initially used in robotics and intelligent agents, the use of planning for testing purposes has increased over the years. There sequences of actions representing interactions with the system under test guide the test execution towards reaching a test purpose. A planning problem is formally defined as a model that resembles the interaction with a real system under test (SUT). The obtained solutions are generated, i.e., the plans, directly correspond to test cases. The planning model offers the possibility to generate test cases with a great variety of interactions without the need for an extensive model definition. Until now, planning has proven to be efficient in detecting both functional and non-functional issues. The second play a major role in uncovering vulnerabilities in software. In fact, testing of any domain can be specified as a planning problem. The purpose of this paper is to summarize previous research in the domain of planning for testing including discussing examples from multiple domains.
Original languageEnglish
Title of host publicationIEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW)
PublisherInstitute of Electrical and Electronics Engineers
Pages23-31
Number of pages9
ISBN (Electronic) 978-1-7281-0888-9
DOIs
Publication statusPublished - 2019
Event12th IEEE International Conference on Software Testing, Verification and Validation - Xi'an, China
Duration: 22 Apr 201927 Apr 2019

Conference

Conference12th IEEE International Conference on Software Testing, Verification and Validation
Abbreviated titleICST 2019
CountryChina
CityXi'an
Period22/04/1927/04/19

Fingerprint Dive into the research topics of 'Software Testing: According to Plan!'. Together they form a unique fingerprint.

Cite this