Skip to main navigation Skip to search Skip to main content

Unit testing tool competitions - Lessons learned

  • Sebastian Bauersfeld*
  • , Tanja E.J. Vos
  • , Kiran Lakhotia
  • *Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference Article in proceedingAcademicpeer-review

Abstract

This paper reports about the two rounds of the Java Unit Testing Tool Competition that ran in the context of the Search Based Software Testing (SBST) workshop at ICST 2013 and the first Future Internet Testing (FITTEST) workshop at ICTSS 2013. It describes the main objectives of the benchmark, the Java classes that were selected in both competitions, the data that was collected, the tools that were used for data collection, the protocol that was carried out to execute the benchmark and how the final benchmark scores for each participating tool were calculated. Eventually, we discuss the challenges encountered during the events, what we learned and how we plan to improve our framework for future competitions.

Original languageEnglish
Title of host publicationFuture Internet Testing - First International Workshop, FITTEST 2013, Revised Selected Papers
PublisherSpringer Verlag
Pages75-94
Number of pages20
Volume84632
ISBN (Print)9783319077840
DOIs
Publication statusPublished - 2014
Externally publishedYes
Event1st International Workshop on Future Internet Testing, FITTEST 2013 - Istanbul, Turkey
Duration: 12 Nov 201312 Nov 2013

Publication series

SeriesLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume8432 LNCS
ISSN0302-9743

Workshop

Workshop1st International Workshop on Future Internet Testing, FITTEST 2013
Abbreviated titleFITTEST 2013
Country/TerritoryTurkey
CityIstanbul
Period12/11/1312/11/13

Keywords

  • Automated unit testing
  • Benchmark
  • Mutation testing

Fingerprint

Dive into the research topics of 'Unit testing tool competitions - Lessons learned'. Together they form a unique fingerprint.

Cite this