paperbot · PL 论文追踪

全部论文 待读 收藏

P2 Practices and tools for better software testing

更好的软件测试:实践与工具
FSE Proceedings of the 2018 26th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering2018匹配度 2/10 · 该论文聚焦软件测试最佳实践与测试代码编写/维护工具,属于软件工程中的测试与开发者工具方向,与用户核心关注的静态分析、LLM/Agent 程序分析、浮点程序分析及贝叶斯程序分析均无明显交集。引用 2 inbox
Davide Spadini
crossref: 2026-09-12

AI 速览

一句话:研究软件测试最佳实践并构建工具,帮助开发者编写和维护更高质量的测试代码。

自动化测试已成为提升软件系统质量的关键手段,但测试代码的编写与维护仍面临挑战,常被管理者与开发者视为次要工作,导致测试代码质量不佳,进而可能产生易缺陷的生产代码。本研究的总体目标是让开发者意识到劣质测试的影响,并帮助他们编写更好的测试代码。研究从两个视角展开:(1) 研究软件测试的最佳实践,识别当前方法存在的问题与挑战;(2) 构建新工具,以更好地支持测试代码编写,并解决先前研究发现的问题。摘要未给出具体评估结果。

问题
自动化测试对软件质量至关重要,但测试代码常被忽视,质量不佳并可能引发生产代码缺陷。
方法
从两方面入手:研究测试最佳实践、识别当前方法与挑战;并构建支持测试代码编写的新工具。
评估
摘要未说明具体评估方式,仅表明研究旨在发现问题并通过工具改进测试实践。
原文摘要(Abstract)

Automated testing (hereafter referred to as just `testing') has become an essential process for improving the quality of software systems. In fact, testing can help to point out defects and to ensure that production code is robust under many usage conditions. However, writing and maintaining high-quality test code is challenging and frequently considered of secondary importance. Managers, as well as developers, do not treat test code as equally important as production code, and this behaviour could lead to poor test code quality, and in the future to defect-prone production code. The goal of my research is to bring awareness to developers on the effect of poor testing, as well as helping them in writing better test code. To this aim, I am working on 2 different perspectives: (1) studying best practices on software testing, identifying problems and challenges of current approaches, and (2) building new tools that better support the writing of test code, that tackle the issues we discovered with previous studies. Pre-print: https://doi.org/10.5281/zenodo.1411241

链接与引用

DOI 原文 · PDF(开放获取) ·

BibTeX
@inproceedings{paperbot4642,
  title = {Practices and tools for better software testing},
  author = {Davide Spadini},
  booktitle = {FSE},
  year = {2018},
  doi = {10.1145/3236024.3275424}
}