Investigating developer perception on test smells using better code hub - Work in progress -

Martin Schvarcbacher, Davide Spadini, Magiel Bruntink, Ana Oprescu

Research output: Chapter in Book/Conference proceedings/Edited volumeConference contributionScientificpeer-review

1 Citation (Scopus)
311 Downloads (Pure)

Abstract

Test smells can be found in test code using a variety of tools. In this paper, we present our integration of a test smell detection tool into Better Code Hub (BCH), an online environment for monitoring code quality and identifying problems in it. We extended BCH with test smell detection and observe how developers react to various instances of test smells. By integrating this detection into BCH, we gain access to a wide range of developers working on both open-source and commercial projects using their own code. We study whether developers consider these test smells important and what they do with them in future code changes. From our preliminary results, we found out a high test smell detection accuracy for most test smells; however, developers are only willing to remove a small portion of them.

Original languageEnglish
Title of host publicationSATTOSE 2019 Seminar Series on Advanced Techniques & Tools for Software Evolution
Subtitle of host publicationProceedings of the Seminar Series on Advanced Techniques & Tools for Software Evolution (SATTOSE 2019)
EditorsAnne Etien
PublisherCEUR-WS
Pages1-6
Number of pages6
Publication statusPublished - 2019
Event2019 Seminar Series on Advanced Techniques and Tools for Software Evolution, SATTOSE 2019 - Bolzano, Italy
Duration: 8 Jul 201910 Jul 2019

Publication series

NameCEUR Workshop Proceedings
Volume2510
ISSN (Print)1613-0073

Conference

Conference2019 Seminar Series on Advanced Techniques and Tools for Software Evolution, SATTOSE 2019
Country/TerritoryItaly
CityBolzano
Period8/07/1910/07/19

Fingerprint

Dive into the research topics of 'Investigating developer perception on test smells using better code hub - Work in progress -'. Together they form a unique fingerprint.

Cite this