Trade-off between automated and manual software testing

@article{Taipale2011TradeoffBA,
  title={Trade-off between automated and manual software testing},
  author={Ossi Taipale and Jussi Kasurinen and Katja Karhu and Kari Smolander},
  journal={International Journal of System Assurance Engineering and Management},
  year={2011},
  volume={2},
  pages={114-125}
}
The study explores the current state of test automation in software testing organizations by focusing on the views and observations of managers, testers and developers in each organization. The case study was conducted in selected organizational units that develop and test technical software for industrial automation or telecommunication domains. The data was collected with 41 theme-based interviews in each unit. The interview data was analyzed qualitatively by using the grounded theory… 
View on Springer
researchgate.net
43 Citations
Highly Influential Citations
3
Background Citations
21
Methods Citations
10

43 Citations

Citation Type

Citation Type

Organization of Testing Activities in Norwegian Software Companies
  • A. Deak, T. Stålhane
  • Business
    2013 IEEE Sixth International Conference on Software Testing, Verification and Validation Workshops
  • 2013
TLDR
This study provides a snapshot of the current trends of organizing software testing activities in Norwegian companies and it is a stepping stone into research of the testing practices and testers' experience.
Relevance and Impact of Critical Factors of Success in Software Test Automation lifecycle: A Survey
TLDR
Evaluating the relevance of 12 critical factors of success (CFS) in software test automation collected from the technical literature according to researchers views found that each factor impacts the BSTAL phases differently and they can be more or less relevant according to the phase under observation.
A survey on software test automation return on investment, in organizations predominantly from Bengaluru, India
TLDR
A survey and analysis is presented to understand the ROI of test automation from industry test professionals from both product and services organizations.
Evidence and perceptions on GUI test automation - An Exploratory Study
TLDR
This study identifies new findings in addition to the existing literature that indicate that the generic testability requirements identified in the literature are also valid for GUI automation testing.
TAPN: Test Automation's Pyramid of Needs
TLDR
A hierarchical model called Test Automation’s Pyramid of Needs (TAPN) is proposed which comprises five levels that influence on the success of test automation initiatives in software organizations and it intends to help organizations to build their test automation strategy using good practices captured from the technical literature.
Decision Support for Selecting Tools for Software Test Automation
TLDR
The goal of the research is to define a systematic, empirically validated decision support system (DSS) for selecting a tool for software test automation.
A Review to Reality of Software Test Automation
TLDR
It was found that there is still no agreement on its definition and the advantages and limitations are almost personal opinions, and many companies assume automation as a total replacement for manual testing, although their level of maturity still not allowed.
Evaluating a model-based software testing approach in an industrial context: A replicated study
TLDR
This paper replicates a previous study that evaluated the use of MBT by software engineers in an industrial context and evaluates the feasibility and acceptance of the MBT approach from the perspective of quality engineers testing a software application in the industry.
When to automate software testing? decision support based on system dynamics: an industrial case study
TLDR
A simulation model is proposed using the System Dynamics (SD) modeling technique that can evaluate the performance of test processes with varying degrees of automation of test activities and help testers choose the most optimal cases.
How can manual testing processes be optimized? developer survey, optimization guidelines, and case studies
Manual software testing is tedious and costly as it involves significant human effort. Yet, it is still widely applied in industry and will be in the foreseeable future. Although there is arguably a…
...
...

References

SHOWING 1-10 OF 58 REFERENCES
Empirical Observations on Software Testing Automation
TLDR
According to the results, the factors which emphasize the wide use of testing automation include that the tested products are generic and independent of third-party systems.
Why Model-Based Test Automation is Different and What You Should Know to Get Started
TLDR
The paper discusses the organizational, personnel, and development lessons learned from working with numerous companies and projects over the past several years, and recommends how to get started, how to select a project, and how to organize a project.
Economic perspectives in test automation: balancing automated and manual testing with opportunity cost
TLDR
An alternative model based on opportunity cost is introduced and influencing factors on the decision of whether or not to invest in test automation are presented and stimulated to stimulate discussion about these factors as well as their influence on the benefits and costs of automated testing.
Testing: a roadmap
TLDR
The state of the art in software testing is assessed, some future directions inSoftware testing are outlined, and some pointers to software testing resources are given.
Observing Software Testing Practice from the Viewpoint of Organizations and Knowledge Management
The objective of this qualitative study was to understand the complex practice of software testing, and based on this understanding, to develop hypotheses on testing organizations and knowledge…
Factors affecting software testing time schedule
TLDR
The analysis revealed that increased communication and interaction in the design phase between development and testing are associated with time schedule over-runs, which is unexpected and can be utilized in planning software testing time schedules.
Finding and Ranking Research Directions for Software Testing
TLDR
A survey was carried out to find out where software testing research should be directed and an example how project steering groups can be used in resolving research priorities is shown.
A preliminary survey on software testing practices in Australia
TLDR
The first survey on software testing practices carried out in Australian ICT industry is presented, as well as some observations and recommendations for the future of software testing in Australia for industry and academia.
Establishment of automated regression testing at ABB: industrial experience report on 'avoiding the pitfalls'
  • C. Persson, Nur Yilmaztürk
  • Engineering
    Proceedings. 19th International Conference on Automated Software Engineering, 2004.
  • 2004
TLDR
The emphasis is put on the importance of incorporating the 'common pitfalls' in the formal risk management throughout the automated testing establishment life cycle, and the effects of such an act on the execution and success of the projects.
Software testing in the real world - improving the process
PART I: Software testing process maturity Chapter 1: The six essentials of software testing Essential 1: The quality of the test process determines the success of the test effort Essential 2: Prevent…
...
...