Test cases: Vendor backend
Nội dung này hiện chưa có sẵn bằng ngôn ngữ của bạn.
Document control
Section titled “Document control”| Version | Date (UTC) | Summary |
|---|---|---|
| 1.0.0 | 2026-05-13 | Initial catalogue for vendor module |
| 1.1.0 | 2026-05-13 | Split inventory, finance, orders; this page = cross-cutting only |
| 1.2.0 | 2026-05-13 | Bulk caps, idempotency, multi-store edge cases |
- HTTP:
auth/vendor/*,vendor/*(Backend modules). - Deep dives:
Scenario catalogue (cross-cutting)
Section titled “Scenario catalogue (cross-cutting)”| ID | Class | Scenario | Automation |
|---|---|---|---|
| TC-VND-001 | Happy | Vendor employee with module lists resource for allowed store | Unit |
| TC-VND-002 | Unhappy | Request without store_id on store-bound endpoint → 400 | Unit |
| TC-VND-003 | Unhappy | Employee uses store_id not on roster → 403 | Unit |
| TC-VND-004 | Happy | Owner token sees all stores under vendor | Unit |
| TC-VND-005 | Unhappy | skipEmployeeStoreId misuse on batch-only DTO → wrong store attachment | Unit |
| TC-VND-006 | Happy | User-notification visibility rules respected on merged feed | Unit |
| TC-VND-007 | Unhappy | Vendor JWT for other tenant’s id → 403 everywhere | Unit |
| TC-VND-008 | Happy | Idempotency-Key header respected on POST payment-like endpoints | Unit |
| TC-VND-009 | Unhappy | Bulk ids over server cap → 400 | Unit |
| TC-VND-010 | Happy | Owner store_id optional paths still resolve correct vendor scope | Unit |
Coverage checklist (this sheet)
Section titled “Coverage checklist (this sheet)”-
store_idmatrix for POS vs dashboard documented in Vendor orders & checkout - New vendor controllers default to a deep sheet unless truly cross-cutting
- Recipient audience constants (Authentication +
user-notification-recipientcode) synced when inserts change
Parent index: System test cases (index)