Proceedings of the 2014 International Conference on Software and System Process 2014
DOI: 10.1145/2600821.2600832
|View full text |Cite
|
Sign up to set email alerts
|

When to automate software testing? decision support based on system dynamics: an industrial case study

Abstract: Software test processes are complex and costly. To reduce testing effort without compromising effectiveness and product quality, automation of test activities has been adopted as a popular approach in software industry. However, since test automation usually requires substantial upfront investments, automation is not always more cost-effective than manual testing. To support decision-makers in finding the optimal degree of test automation in a given project, we propose in this paper a simulation model using th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
18
0

Year Published

2015
2015
2020
2020

Publication Types

Select...
7

Relationship

4
3

Authors

Journals

citations
Cited by 23 publications
(18 citation statements)
references
References 16 publications
0
18
0
Order By: Relevance
“…Since the adoption of automated testing in the Turkish industry is very low, it seems that most Turkish SE practitioners are unaware of the advantages of automated testing. Thus, we recommend to the practitioners reviewing the success stories of adopting automated testing, e.g., [54][55][56][57]  There is only one vote by a respondent for the "always-always" combination ("always" conducting both manual and automated testing).…”
Section: Figure 34-manual Versus Automated Testingmentioning
confidence: 99%
“…Since the adoption of automated testing in the Turkish industry is very low, it seems that most Turkish SE practitioners are unaware of the advantages of automated testing. Thus, we recommend to the practitioners reviewing the success stories of adopting automated testing, e.g., [54][55][56][57]  There is only one vote by a respondent for the "always-always" combination ("always" conducting both manual and automated testing).…”
Section: Figure 34-manual Versus Automated Testingmentioning
confidence: 99%
“…As Figure 3 shows, in our research methodology, we also gathered inputs from our personal experience and qualitative evidence in the projects, the papers which have resulted from those projects (e.g., [52][53][54][55][56][57][58][59]), additional email and personal communication with the project staff at the time of working on this paper, and finally from the recent SLR study [3] about the set of challenges, patterns and anti-patterns that we chose as baselines.…”
Section: Research Methodology and Synthesis Methodsmentioning
confidence: 99%
“… AP9: Insufficient benefits presentation: This issue did occur in project TR2 and was discussed above.  AP12: Using lab experiments for argumentation before convincing stakeholders: While we conducted lab experiments before trying out the research approaches in industry, e.g., in [52,54,81], this anti-pattern occurred in some cases, e.g., lab experiments were simply not possible (due to shortage of hypothetic data in lab settings, e.g., [56,57]) or was too time consuming.  AP17: Not distinguishing experimental environment from real-life situations: This anti-pattern slightly overlaps with the one above (AP12).…”
Section: (Initial Development)+87*2 (Test Code Maintenance)-120(autobmentioning
confidence: 99%
“…Testing processes are complex and costly, and in order to reduce efforts, without compromising product effectiveness and quality, automation of testing activities has been adopted as a popular approach in software factories (Sahaf et al, 2014). Nevertheless, automation usually requires substantial investment and will not always be more cost effective than manual testing.…”
Section: Introductionmentioning
confidence: 99%