![]() Statements from the publications are synthesized, based on a thematic coding, into 24 challenges related to GUI test automation. The review is based on a final set of 49 publications, all reporting empirical evidence from practice or industrial studies. This systematic literature review takes a longitudinal perspective on GUI test automation challenges by identifying them and then investigating why the field has been unable to mitigate them for so many years. Furthermore, the software industry has struggled with some of these challenges for more than a decade with what seems like only limited progress. However, we have not yet seen the same convincing results for automated GUI-based testing, which has instead been associated with multiple technical challenges. Automation has been successful in reducing costs for other forms of testing (like unit- or integration testing) in industrial practice. GUI-based test automation, like other automation, aims to reduce the cost and time for testing compared to alternative, manual approaches. The need to raise consciousness that automated testing means programming solved most of the initial problems.Īutomated testing is ubiquitous in modern software development and used to verify requirement conformance on all levels of system abstraction, including the system’s graphical user interface (GUI). However, it became clear that this could be solved by explaining the need for these oracles and compare them to the alternative of more expensive and complex human oracles. Finally, the need to program Java-code to create sophisticated oracles for testing created some initial problems and some resistance. The training materials as well as the user and installation manual of TESTAR need to be improved using the feedback received during the study. The effectiveness and efficiency of the automated tests generated with TESTAR can definitely compete with that of the manual test suite. On the other hand, we were interested to see how easy or difficult it is to learn and implant our academic prototype within an industrial setting. The goal of the study was to evaluate how the tool would perform within the context of SOFTEAM and on their software application. ![]() The case study was conducted at SOFTEAM, a French software company, while testing their Modelio SaaS system, a cloud-based system to manage virtual machines that run their popular graphical UML editor Modelio. This paper aims at the evaluation of TESTAR with an industrial case study. In previous work we have described TESTAR, a tool which allows to set-up fully automatic testing at the GUI level of applications to find severe faults such as crashes or non-responsiveness. Tests are still mainly designed and executed manually. Automated test case design and execution at the GUI level of applications is not a fact in industrial practice.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |