Search: id:"swepub:oai:DiVA.org:bth-21820" >
A Failed attempt at...
A Failed attempt at creating Guidelines for Visual GUI Testing : An industrial case study
-
- Alégroth, Emil, 1984- (author)
- Blekinge Tekniska Högskola,Institutionen för programvaruteknik,Blekinge Inst Technol, Sweden
-
- Borch Petersen, Eline (author)
- Linköpings universitet,Avdelningen för Logopedi, Audiologi och Otorhinolaryngologi,Medicinska fakulteten,Linköping University, SWE
-
- Tinnerholm, John (author)
- Linköpings universitet,Programvara och system,Tekniska fakulteten,Linköping University, SWE
-
(creator_code:org_t)
- Institute of Electrical and Electronics Engineers Inc. 2021
- 2021
- English.
-
In: Proceedings - 2021 IEEE 14th International Conference on Software Testing, Verification and Validation, ICST 2021. - : Institute of Electrical and Electronics Engineers Inc.. - 9781728168364 ; , s. 340-350
- Related links:
-
https://bth.diva-por... (primary) (Raw object)
-
show more...
-
https://urn.kb.se/re...
-
https://doi.org/10.1...
-
https://urn.kb.se/re...
-
show less...
Abstract
Subject headings
Close
- Software development is governed by guidelines that aim to improve the code's qualities, such as maintainability. However, whilst coding guidelines are commonplace for software, guidelines for testware are much less common. In particular, for GUI-based tests driven with image recognition, also referred to as Visual GUI Testing (VGT), explicit coding guidelines are missing.In this industrial case study, performed at the Swedish defence contractor Saab AB, we propose a set of coding guidelines for VGT and evaluate their impact on test scripts for an industrial, safety-critical system. To study the guidelines' effect on maintenance costs, five representative manual test cases are each translated with and without the proposed guidelines in the two VGT tools SikuliX and EyeAutomate. As such, 20 test scripts were developed, with a combined development cost of more than 100 man-hours. Three of the tests are then maintained by one researcher and two practitioners for another version of the system and costs measured to evaluate return on investment. This analysis is complemented with observations and interviews to elicit practitioners' perceptions and experiences with VGT.Results show that scripts developed with the guidelines had higher maintenance costs than scripts developed without guidelines. This is supported by qualitative results that many of the guidelines are considered inappropriate, superfluous or unnecessary due to the inherent properties of the scripts, e.g. their natural small size, linear flows, natural separation of concerns, and more. We conclude that there are differences between VGT scripts and software that prohibit direct translation of guidelines between the two. As such, we consider our study as a failure but argue that several lessons can be drawn from our results to guide future research into guidelines for VGT and GUI-based test automation. © 2021 IEEE.
Subject headings
- NATURVETENSKAP -- Data- och informationsvetenskap -- Programvaruteknik (hsv//swe)
- NATURAL SCIENCES -- Computer and Information Sciences -- Software Engineering (hsv//eng)
Keyword
- Automated Testing
- Case study
- Guidelines for testing
- Industrial study
- Visual GUI testing
- Accident prevention
- Cost benefit analysis
- Costs
- Graphical user interfaces
- Image coding
- Image recognition
- Maintenance
- Safety testing
- Software design
- Verification
- Defence contractors
- Development costs
- Industrial case study
- Maintenance cost
- Safety critical systems
- Separation of concerns
- Test Automation
- Software testing
Publication and Content Type
- ref (subject category)
- kon (subject category)
Find in a library
To the university's database