fix: 认证策略是先充值后实名, 首页入口
All checks were successful
构建并部署前端到生产环境 / build-and-deploy (push) Successful in 1m11s
All checks were successful
构建并部署前端到生产环境 / build-and-deploy (push) Successful in 1m11s
This commit is contained in:
@@ -18,10 +18,17 @@ The H5/C client SHALL use `GET /api/c/v1/asset/info?identifier=...` as the sourc
|
||||
|
||||
#### Scenario: Real name is required after ordering
|
||||
|
||||
- **WHEN** asset information returns `effective_realname_policy = after_order`
|
||||
- **THEN** the client SHALL allow the policy-defined post-order flow to proceed without applying a before-order block
|
||||
- **AND** the client SHALL display the returned real-name status
|
||||
- **AND** selecting the homepage real-name entry SHALL show a confirmation prompt and allow the user to navigate to package ordering instead of entering real-name authentication directly
|
||||
- **WHEN** the effective real-name policy is `after_order`
|
||||
- **AND** `/api/c/v1/device/cards` returns no card with completed real-name authentication
|
||||
- **AND** package history contains neither a pending package (`status = 0`) nor an active package (`status = 1`)
|
||||
- **THEN** selecting a real-name entry on the homepage or operator-switch page SHALL block direct real-name authentication
|
||||
- **AND** the client SHALL show a confirmation prompt that can navigate to package ordering
|
||||
|
||||
#### Scenario: Post-order real-name requirement is satisfied
|
||||
|
||||
- **WHEN** the effective real-name policy is `after_order`
|
||||
- **AND** `/api/c/v1/device/cards` returns at least one authenticated card, or package history contains a pending or active package
|
||||
- **THEN** the homepage and operator-switch real-name entries SHALL retain the existing real-name authentication flow
|
||||
|
||||
#### Scenario: Device status is resolved from server output
|
||||
|
||||
|
||||
Reference in New Issue
Block a user