artifact: add FPA analysis outputs through round 6
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
Feature: invite-code-verification
|
||||
|
||||
Scenario: Happy Path
|
||||
Given Client 通过邀请链接进入邀请进入页,且持有有效的邀请码
|
||||
When Client 输入邀请码并提交验证
|
||||
Then 系统应完成身份确认并允许 Client 进入后续注册流程
|
||||
|
||||
Scenario: Permission Case
|
||||
Given Firm Owner 尝试代替受邀 Client 进入邀请码验证后的注册流程
|
||||
When Firm Owner 提交验证请求
|
||||
Then 系统应拒绝其进入后续注册步骤,并保持受邀入口只服务正确对象
|
||||
|
||||
Scenario: Error Case
|
||||
Given Client 输入的邀请码错误、已过期或验证服务异常
|
||||
When Client 提交邀请码
|
||||
Then 系统应明确提示验证失败原因,而不是让 Client 落入不明状态
|
||||
|
||||
Scenario: Edge Case
|
||||
Given Client 打开的邀请链接有效,但输入的邀请码已被其他流程标记为已使用
|
||||
When Client 尝试完成身份确认
|
||||
Then 系统应把该状态解释清楚,并指导 Client 联系事务所或重新获取邀请
|
||||
|
||||
Scenario: Accessibility Case
|
||||
Given Client 依赖键盘导航或屏幕阅读器输入邀请码
|
||||
When Client 浏览输入框、校验提示与继续按钮
|
||||
Then 系统应让字段名称、错误信息与验证结果可以被顺序访问并清晰朗读
|
||||
Reference in New Issue
Block a user