Software test-code engineering: A systematic mapping

Date

2015-02-01

Author

Yusifoglu, Vahid Garousi
Amannejad, Yasaman
Betin Can, Aysu

Metadata

Show full item record

This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.

Item Usage Stats

213
views

0
downloads

Context: As a result of automated software testing, large amounts of software test code (script) are usually developed by software teams. Automated test scripts provide many benefits, such as repeatable, predictable, and efficient test executions. However, just like any software development activity, development of test scripts is tedious and error prone. We refer, in this study, to all activities that should be conducted during the entire lifecycle of test-code as Software Test-Code Engineering (STCE).

Subject Keywords

Systematic mapping, Survey; Study repository, Software test-code engineering, Development of test code, Quality assessment of test code

URI

https://hdl.handle.net/11511/30483

Journal

INFORMATION AND SOFTWARE TECHNOLOGY

DOI

https://doi.org/10.1016/j.infsof.2014.06.009

Collections

Graduate School of Informatics, Article

Suggestions

OpenMETU
Core

Software Repository Analysis for Investigating Design-Code Compliance OZBAS-CAGLAYAN, Kadriye; Doğru, Ali Hikmet (2013-10-26) Compliance check between code and design is a labor-intensive job to do, since it requires the code to be reverse engineered and checked versus design manually. On the other hand, investigation of the design-code compliance would give some valuable information to software development and maintenance managers. In this study, an approach for employing software repository analysis and text mining techniques to extract and analyze compliance levels of design and code efficiently is presented.
Graphical user interface (GUI) testing: Systematic mapping and repository Banerjee, Ishan; Nguyen, Bao; Garousi, Vahid; Memon, Atif (Elsevier BV, 2013-10-01) Context: GUI testing is system testing of a software that has a graphical-user interface (GUI) front-end. Because system testing entails that the entire software system, including the user interface, be tested as a whole, during GUI testing, test cases-modeled as sequences of user input events-are developed and executed on the software by exercising the GUI's widgets (e.g., text boxes and clickable buttons). More than 230 articles have appeared in the area of GUI testing since 1991.
Software process improvement Elalmış, Mert Erkan; Yücel, Melek D; Department of Electrical and Electronics Engineering (2007) In this thesis the software development process and in particular, the requirements management processes in a major software development company have been investigated. The current problems related to requirements quality and process performances have been identified. Process improvement measures have been proposed based on the suggestions found in the relevant literature. The current process and the improved version have been compared with respect to the process evaluation metrics proposed particularly for...
Software test maturity assessment and test process improvement: A multivocal literature review Garousi, Vahid; Felderer, Michael; Hacaloglu, Tuna (Elsevier BV, 2017-05-01) Context: Software testing practices and processes in many companies are far from being mature and are usually conducted in ad-hoc fashions. Such immature practices lead to various negative outcomes, e.g., ineffectiveness of testing practices in detecting all the defects, and cost and schedule overruns of testing activities. To conduct test maturity assessment (TMA) and test process improvement (TPI) in a systematic manner, various TMA/TPI models and approaches have been proposed.
A survey of software testing practices in Canada Garousi, Vahid; Zhi, Junji (2013-05-01) Software testing is an important activity in the software development life-cycle. In an earlier study in 2009, we reported the results of a regional survey of software testing practices among practitioners in the Canadian province of Alberta. To get a larger nationwide view on this topic (across Canada), we conducted a newer survey with a revised list of questions in 2010. Compared to our previous Alberta-wide survey (53 software practitioners), the nation-wide survey had larger number of participants (246 ...

Citation Formats

V. G. Yusifoglu, Y. Amannejad, and A. Betin Can, “Software test-code engineering: A systematic mapping,” INFORMATION AND SOFTWARE TECHNOLOGY, pp. 123–147, 2015, Accessed: 00, 2020. [Online]. Available: https://hdl.handle.net/11511/30483.