A Trend Analysis of Test Smells in Python Test Code Over Commit History

Software testing is an essential activity for developing and maintaining high-quality software. Unit testing with test code (test cases) is a fundamental testing activity, and developers can test their production code whenever they create or modify the code. However, such quality assurance relies on...

Celý popis

Uloženo v:
Podrobná bibliografie
Vydáno v:Proceedings (EUROMICRO Conference on Software Engineering and Advanced Applications. Online) s. 310 - 314
Hlavní autoři: Fushihara, Yuki, Aman, Hirohisa, Amasaki, Sousuke, Yokogawa, Tomoyuki, Kawahara, Minoru
Médium: Konferenční příspěvek
Jazyk:angličtina
Vydáno: IEEE 06.09.2023
Témata:
ISSN:2376-9521
On-line přístup:Získat plný text
Tagy: Přidat tag
Žádné tagy, Buďte první, kdo vytvoří štítek k tomuto záznamu!
Popis
Shrnutí:Software testing is an essential activity for developing and maintaining high-quality software. Unit testing with test code (test cases) is a fundamental testing activity, and developers can test their production code whenever they create or modify the code. However, such quality assurance relies on the correctness of the test code. If a test code had a flaw, it would mislead the developers about the hidden faults and prevent early detection of the faults. This paper focuses on "test smells," which may cause test code flaws in Python programs, and analyzes their changing trends over commit history (code changes) toward better Python test code management. Through an empirical data analysis of 100 open-source projects, the paper reports the following findings: (1) a few kinds of test smells constitute the majority of smells detected in the studied projects, and (2) most kinds of smells tend to increase over commits, i.e., many test smells are likely to have remained in test code as technical debt.
ISSN:2376-9521
DOI:10.1109/SEAA60479.2023.00054