artifact: add FPA analysis outputs through round 6
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
Feature: owner-daily-briefing
|
||||
|
||||
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