论文标题
是什么使敏捷测试工件有用？从从业者的角度来看的基于活动的质量模型
What Makes Agile Test Artifacts Useful? An Activity-Based Quality Model from a Practitioners' Perspective
论文作者
论文摘要
背景：敏捷软件测试中使用的工件以及使用这些工件的原因相当充分理解。但是，关于最终如何在实践中设计敏捷测试工件以及哪些质量因素使其对软件测试有用的实证研究仍然很少。目的：我们的目标是两个方面。首先，我们确定了使用测试工件以了解为什么某些质量因素被认为是好是坏的挑战。其次，我们构建了一个基于活动的人工质量模型，该模型描述了敏捷测试工件的外观。方法：我们对来自七个不同领域的12家公司的18家从业者进行了工业调查。结果：我们的分析揭示了9个挑战和16个因素，从敏捷测试者的角度来描述了六个测试工件的质量。有趣的是，我们观察到有关语言和可追溯性的挑战，这些挑战是在非敏捷项目中众所周知的。结论：尽管敏捷软件测试已成为常态，但我们对将军的DO和不超越传统智慧的信心仍然没有信心。这项研究是第一个提炼质量因素列表的列表，而这些因素被认为是可以被认为是有用的测试工件的重要因素。
Background: The artifacts used in Agile software testing and the reasons why these artifacts are used are fairly well-understood. However, empirical research on how Agile test artifacts are eventually designed in practice and which quality factors make them useful for software testing remains sparse. Aims: Our objective is two-fold. First, we identify current challenges in using test artifacts to understand why certain quality factors are considered good or bad. Second, we build an Activity-Based Artifact Quality Model that describes what Agile test artifacts should look like. Method: We conduct an industrial survey with 18 practitioners from 12 companies operating in seven different domains. Results: Our analysis reveals nine challenges and 16 factors describing the quality of six test artifacts from the perspective of Agile testers. Interestingly, we observed mostly challenges regarding language and traceability, which are well-known to occur in non-Agile projects. Conclusions: Although Agile software testing is becoming the norm, we still have little confidence about general do's and don'ts going beyond conventional wisdom. This study is the first to distill a list of quality factors deemed important to what can be considered as useful test artifacts.
