一句话：首次细粒度实证研究真实 Java 项目中测试注解变更，揭示其频率、迁移模式与变更动机。
Java 5 引入注解后，JUnit、TestNG、Mockito 等测试框架广泛采用注解，影响测试生命周期各环节。但已有测试维护研究多关注测试代码质量和断言，缺乏对测试注解演化与维护的实证证据。本文开发工具挖掘 12 个开源 Java 项目的 82,810 次提交，检测出 23,936 个测试注解变更实例。作者分析常见注解替换模式，以恢复同一测试框架内或不同框架间的迁移努力；并人工检查分类 368 个变更样本，建立分类体系并记录变更动机。主要发现包括：测试注解变更比重命名和类型变更重构更频繁；可观察到多种框架迁移模式；最后为开发者、研究者和框架设计者给出一系列可操作启示。
Since the introduction of annotations in Java 5, the majority of testing frameworks, such as JUnit, TestNG, and Mockito, have adopted annotations in their core design. This adoption affected the testing practices in every step of the test life-cycle, from fixture setup and test execution to fixture teardown. Despite the importance of test annotations, most research on test maintenance has mainly focused on test code quality and test assertions. As a result, there is little empirical evidence on the evolution and maintenance of test annotations. To fill this gap, we perform the first fine-grained empirical study on annotation changes. We developed a tool to mine 82,810 commits and detect 23,936 instances of test annotation changes from 12 open-source Java projects. Our main findings are: (1) Test annotation changes are more frequent than rename and type change refactorings. (2) We recover various migration efforts within the same testing framework or between different frameworks by analyzing common annotation replacement patterns. (3) We create a taxonomy by manually inspecting and classifying a sample of 368 test annotation changes and documenting the motivations driving these changes. Finally, we present a list of actionable implications for developers, researchers, and framework designers.