test(ratchet): f43ed6f1 落地时漏改的两处陈旧钉按实测重新上钉
这两支红在 HEAD 上(不是工作树):f43ed6f1「任务中断+继续」当时只跑了定向
79+22 与 ops 快检,没点后端整量,于是两支钉死分母跟着功能一起陈旧。本笔不放宽,
只是把覆盖面变大如实记账——与文件里既有的 126→128 那条同一写法。
- ResultFileJobHandlerTest.interfaceMethodsPresent 9→10:接口新增第 10 枚
default onTaskResumed(Long)(继续续跑前清模块补检预算,AP 侧删 __recheck__
哨兵键;不清则"继续"后第一轮就被"补检已耗尽"直接按部分表收尾)。断言里
同时补上对 onTaskResumed 的 methodOf 存在性核对,别只数个数。
- RequestSuppliedIdentityOutletTest 写类分母 128→129:TaskHeartbeatController
POST /api/tasks/{taskId}/interrupt 是新增的写类端点,@RequestParam("user_id")
先过 adminAuthSupport.resolveOwnershipUserId 再比归属(:52-57 实核)。
This commit is contained in:
+3
-1
@@ -95,7 +95,9 @@ class RequestSuppliedIdentityOutletTest {
|
||||
// 128 而不是 126:2026-11-01「失败任务在原任务上重试」新增两支写类端点(TaskRetryController
|
||||
// POST /api/tasks/{taskId}/retry + AppearancePatentController POST /tasks/{taskId}/retry),
|
||||
// 两边都是 @RequestParam("user_id") 先过 resolveOwnershipUserId——记账变大是覆盖面变大,不是放宽分母。
|
||||
assertThat(scan.boundWrite()).as("取请求身份且已接出口的写类 handler 数").isEqualTo(128);
|
||||
// 129 而不是 128:2026-11-03 f43ed6f1「任务中断+继续」新增 TaskHeartbeatController
|
||||
// POST /api/tasks/{taskId}/interrupt,鉴权镜像 retry(先过 resolveOwnershipUserId 再比归属)。
|
||||
assertThat(scan.boundWrite()).as("取请求身份且已接出口的写类 handler 数").isEqualTo(129);
|
||||
// 64 而不是 63:2026-10-29 随本地采集开关恢复 GET /tasks/{taskId}/queue-payload,
|
||||
// 该 handler 同时接上 resolveOwnershipUserId(不是放宽分母)。
|
||||
assertThat(scan.boundRead()).as("取请求身份且已接出口的读类 handler 数").isEqualTo(64);
|
||||
|
||||
+8
-3
@@ -40,15 +40,20 @@ class ResultFileJobHandlerTest {
|
||||
void interfaceMethodsPresent() throws Exception {
|
||||
// 2026-09:新增 resolveResultFileUrl(模块自定义结果对象 key 解析,BRAND 用),
|
||||
// 接口方法从 8 个增到 9 个,同步更新契约断言。
|
||||
assertEquals(9, ResultFileJobHandler.class.getDeclaredMethods().length,
|
||||
"接口方法数量为 9(moduleType/process/onSuccess/cleanup/onFailure/"
|
||||
+ "fallbackAssembleOnFailure/resolveResultFileUrl/supportsAsyncOffload/isOwnerScoped)");
|
||||
// 2026-11-03 f43ed6f1「任务中断+继续」:新增 onTaskResumed 钩子(继续在原任务上续跑前
|
||||
// 清模块补检预算,AP 侧删 __recheck__ 哨兵键),9 个增到 10 个。分母变大是覆盖面变大,
|
||||
// 不是放宽——少一个钩子=继续跑的任务第一轮就被「补检已耗尽」按部分表收尾。
|
||||
assertEquals(10, ResultFileJobHandler.class.getDeclaredMethods().length,
|
||||
"接口方法数量为 10(moduleType/process/onSuccess/cleanup/onFailure/"
|
||||
+ "fallbackAssembleOnFailure/resolveResultFileUrl/onTaskResumed/"
|
||||
+ "supportsAsyncOffload/isOwnerScoped)");
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "moduleType"));
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "process", TaskFileJobEntity.class));
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "onSuccess", TaskFileJobEntity.class));
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "cleanup", TaskFileJobEntity.class));
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "onFailure", TaskFileJobEntity.class, String.class));
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "resolveResultFileUrl", TaskFileJobEntity.class));
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "onTaskResumed", Long.class));
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "supportsAsyncOffload"));
|
||||
assertNotNull(methodOf(ResultFileJobHandler.class, "isOwnerScoped"));
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user