When deadlines and resources of software projects become scarce, testing is usually in the first row to have its activities aborted or reduced; however, if defects cannot be found, product quality can be affected. In the software development process, aborted or reduced activities that can bring short-term benefits, but can be harmful to the project in the long run, are considered Technical Debt (TD) and, when the TDs impact testing activities, they are called Test Debt. Although there are several studies dealing with Test Debt, current solutions often deal with specific types of tests (e.g., exploratory and automated tests) and do not address the whole software testing process. Aiming to fill these gaps, this work then proposes a Test Debt Catalog, called TestDCat, with subtypes of Test Debts and Technical Debt management activities. This catalog is built based on the results of an empirical study, a literature review and semi-structured interviews conducted with practitioners who perform testing activities on five projects from industry. For the TestDCat evaluation, a case study is conducted in real projects in order to identify if the catalog is user-friendly and if its use helps the Test Debt management during the execution of test activities in these software development projects.

当软件项目的截止日期和资源变得稀缺时，通常在第一行进行测试以中止或减少其活动。但是，如果找不到缺陷，则会影响产品质量。在软件开发过程中，中止或减少的活动可以带来短期利益，但从长远来看可能对项目有害，因此被视为技术债务（TD），当TD影响测试活动时，它们被称为测试。债务。尽管有许多研究涉及测试债务，但是当前的解决方案通常处理特定类型的测试（例如探索性测试和自动化测试），并且无法解决整个软件测试过程。为了填补这些空白，这项工作然后提出了一个名为TestDCat的测试债务目录，其中包含测试债务和技术债务管理活动的子类型。该目录是根据对五个行业项目进行测试活动的从业人员进行的实证研究，文献综述和半结构化访谈的结果而建立的。对于TestDCat评估，将在实际项目中进行案例研究，以确定目录是否易于使用，以及在这些软件开发项目中执行测试活动期间目录的使用是否有助于测试债务管理。