artifact: add FPA analysis outputs through round 6
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
Feature: accountant-workload-and-assignment
|
||||
|
||||
Scenario: Happy Path
|
||||
Given Firm Owner 打开团队推进页,且系统已汇总每位会计师的客户数、案件数、临期压力、缺件积压与风险事项
|
||||
When Firm Owner 查看会计师负载并将一个案件重新分配给更合适的会计师
|
||||
Then 系统应更新案件归属与后续跟进责任,并让团队负载判断保持清晰可追踪
|
||||
|
||||
Scenario: Permission Case
|
||||
Given Accountant 尝试进入会计师负载与分配管理区
|
||||
When Accountant 查看团队级负载与分配入口
|
||||
Then 系统应限制其执行团队分配调整,并保持该能力只属于 Firm Owner
|
||||
|
||||
Scenario: Error Case
|
||||
Given Firm Owner 发起案件重新分配,但目标会计师不可用或分配写入失败
|
||||
When Firm Owner 提交新的归属关系
|
||||
Then 系统应明确提示分配失败原因,并保持原有负责人不被静默覆盖
|
||||
|
||||
Scenario: Edge Case
|
||||
Given Firm Owner 查看团队负载时,发现两位会计师的总体案件数相近,但其中一位存在更高的临期压力与风险积压
|
||||
When Firm Owner 比较团队负载
|
||||
Then 系统应突出显示真实的推进压力差异,而不是仅按案件数量给出误导性结论
|
||||
|
||||
Scenario: Accessibility Case
|
||||
Given Firm Owner 依赖键盘导航或屏幕阅读器浏览团队推进页
|
||||
When Firm Owner 顺序查看负载指标、负责人列表与分配动作
|
||||
Then 系统应让负载信息、责任变化与操作结果可以被顺序访问并清晰朗读
|
||||
Reference in New Issue
Block a user