Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Towards a Hybrid Testing Process Unifying Exploratory Testing and Scripted Testing
Blekinge Institute of Technology, School of Computing.ORCID iD: 0000-0002-1532-8223
2014 (English)In: Journal of Software: Evolution and Process, ISSN 2047-7481, Vol. 26, no 2, p. 220-250Article in journal (Refereed) Published
Abstract [en]

Context: Given the current state of the art in research, practitioners are faced with the challenge of choosing scripted testing (ST) or exploratory testing (ET). Objective: This study aims at systematically incorporating strengths of ET and ST in a hybrid testing process to overcome the weaknesses of each. Method: We utilized systematic review and practitioner interviews to identify strengths and weaknesses of ET and ST. Strengths of ET were mapped to weaknesses of ST, and vice versa. Noblit and Hare’s Lines of Argument method was used for data analysis. The results of the mapping were used as input to co-design a hybrid process with experienced practitioners. Results: We found a clear need to create a hybrid process as: 1) both ST and ET provide strengths and weaknesses and these depend on some particular conditions, which prevents preference of one approach to another, and 2) the mapping showed that it is possible to address the weaknesses in one process by the strengths of the other in a hybrid form. With the input from literature and industry experts a flexible and iterative hybrid process was designed. Conclusions: Practitioners can clearly benefit from using a hybrid process given the mapping of advantages and disadvantages.

Place, publisher, year, edition, pages
Wiley , 2014. Vol. 26, no 2, p. 220-250
Keywords [en]
Software Process improvement, Test process, Prescriptive testing, Scripted testing, Test case based testing, Exploratory testing, Ad hoc testing, Empirical study
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-6719DOI: 10.1002/smr.1621ISI: 000331129000003Local ID: oai:bth.se:forskinfo957C41BCF7FD4F07C1257BC6002E059AOAI: oai:DiVA.org:bth-6719DiVA, id: diva2:834252
Available from: 2014-04-23 Created: 2013-08-13 Last updated: 2021-06-11Bibliographically approved

Open Access in DiVA

fulltext(226 kB)633 downloads
File information
File name FULLTEXT01.pdfFile size 226 kBChecksum SHA-512
c04c14eb27e70607de02fb48dc2a72b5440bc99411550b576130e7de6c06d8cd668f6ef75b9709ca04906d97a3d89a55644ee4c25c9b16c232d913f091a6b304
Type fulltextMimetype application/pdf

Other links

Publisher's full text

Authority records

Petersen, Kai

Search in DiVA

By author/editor
Petersen, Kai
By organisation
School of Computing
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 633 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 269 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf