论文标题
开放和封闭的源项目的测试案例优先级有何不同？
How Different is Test Case Prioritization for Open and Closed Source Projects?
论文作者
论文摘要
改进的测试案例优先级意味着软件开发人员可以比平常更快地检测和修复更多的软件故障。但是，有一种“最佳”优先算法算法？还是各种项目应该得到特殊的优先级？为了回答这些问题，本文将9个优先级方案应用于31个项目，范围从（a）高度评级的开源GitHub项目到（b）计算科学软件到（c）封闭式项目。我们发现，最适合开源项目的优先级方法可以为封闭式项目（反之亦然）效果最差。从这些实验中，我们得出结论，（a）始终将一个优先级方案应用于所有项目是不明智的，因为（b）优先级需要对不同的项目类型进行调整。
Improved test case prioritization means that software developers can detect and fix more software faults sooner than usual. But is there one "best" prioritization algorithm? Or do different kinds of projects deserve special kinds of prioritization? To answer these questions, this paper applies nine prioritization schemes to 31 projects that range from (a) highly rated open-source Github projects to (b) computational science software to (c) a closed-source project. We find that prioritization approaches that work best for open-source projects can work worst for the closed-source project (and vice versa). From these experiments, we conclude that (a) it is ill-advised to always apply one prioritization scheme to all projects since (b) prioritization requires tuning to different project types.
