Challenges and Perils of Testing Database Manipulation Code

Maxime Gobert, Csaba Nagy, Henrique Rocha, Serge Demeyer, Anthony Cleve

Research output: Contribution in Book/Catalog/Report/Conference proceedingConference contribution

5 Downloads (Pure)

Abstract

Software testing enable development teams to maintain thequality of a software system while it evolves. The database manipu-lation code requires special attention in this context. However, it isoften neglected and suffers from software maintenance problems. In thispaper, we investigate the current state-of-the-practice in testing databasemanipulation code. We first analyse the code of 72 projects mined fromLibraries.io to get an impression of the test coverage for database code.We confirm that the database is poorly tested: 46% of the projects didnot cover with tests half of their database access methods, and 33%of the projects did not cover the database code at all. To understandthe difficulties in testing database code, we analysed 532 questions onStackExchange sites and deduced a taxonomy. We found that developersmostly look for insights on general best practices to test database accesscode. They also have more technical questions related to DB handling,mocking, parallelisation or framework/tool usage. This investigation laysthe basis for future research on improving database code testing
Original languageEnglish
Title of host publicationProceedings of the 33rd International Conference on Advanced Information Systems Engineering (CAiSE 2021)
PublisherSpringer
Number of pages17
Publication statusPublished - 2021
Event33rd International Conference on Advanced Information Systems Engineering - Melbourne, Australia
Duration: 28 Jun 20212 Jul 2021
Conference number: 33

Conference

Conference33rd International Conference on Advanced Information Systems Engineering
Abbreviated titleCAISE '21
Country/TerritoryAustralia
CityMelbourne
Period28/06/212/07/21

Keywords

  • testing
  • database manipulation code
  • Empirical study

Fingerprint

Dive into the research topics of 'Challenges and Perils of Testing Database Manipulation Code'. Together they form a unique fingerprint.

Cite this