“让测试通过”的委派可修改实现或降低测试预期
原文依据:4 处示例任务允许子代理在发现问题时修改中止实现,也允许因“行为已改变”而调整测试预期。由于首要目标被表述为让测试通过,子代理可能通过接受错误的新行为来获得绿色测试,而不是修复回归。
产品缺陷可能被较弱或错误的测试预期掩盖;生产代码也可能在没有用户逐项批准的情况下发生持久修改。完整测试全部通过仍不能发现已被改写掉的正确要求。
这是一个有条件的决策完整性风险。Skill 将目标设为“让测试通过”,并在示例中明确允许子代理修改实现,或在其判断行为已变化时调整测试预期。若缺少独立规格或人工审查,子代理可能把回归重新定义为预期行为,从而得到绿色测试却掩盖缺陷。不过,Skill 同时要求审查摘要、检查冲突、运行完整测试和抽查,因此并非无条件接受修改,也不能据此断言实际发生了降级。用户可要求任何预期变更必须引用已批准规格并单独确认。
Each agent gets:- **Specific scope:** One test file or subsystem- **Clear goal:** Make these tests pass- **Constraints:** Don't change other code- **Expected output:** Summary of what you found and fixed查看另外 3 个位置
These are timing/race condition issues. Your task:1. Read the test file and understand what each test verifies2. Identify root cause - timing issues or actual bugs?3. Fix by: - Replacing arbitrary timeouts with event-based waiting - Fixing bugs in abort implementation if found - Adjusting test expectations if testing changed behaviorDo NOT just increase timeouts - find the real issue.Return: Summary of what you found and what you fixed.```1. Read the test file and understand what each test verifies2. Identify root cause - timing issues or actual bugs?3. Fix by: - Replacing arbitrary timeouts with event-based waiting - Fixing bugs in abort implementation if found - Adjusting test expectations if testing changed behaviorDo NOT just increase timeouts - find the real issue.After agents return:1. **Review each summary** - Understand what changed2. **Check for conflicts** - Did agents edit same code?3. **Run full suite** - Verify all fixes work together4. **Spot check** - Agents can make systematic errors