docs: add notification and concurrency test procedures
This commit is contained in:
@@ -21,6 +21,8 @@ seller, payment scanner, delivery, payout, dispute, and deployment behavior.
|
||||
| [[Test Scenario Catalog]] | Canonical scenarios we have designed or need to extend. |
|
||||
| [[Escrow Marketplace E2E Procedure]] | Buyer/seller/request/bid/delivery procedure, including the current two-round flow. |
|
||||
| [[Scanner BSC Testnet Payment Procedure]] | BSC Testnet tUSDT scanner payment procedure and failure modes. |
|
||||
| [[Notification Assertion Procedure]] | Required notification checks after every E2E business step. |
|
||||
| [[Concurrency and Performance Profile]] | Ramp test design, profiling targets, metrics, and report template. |
|
||||
| [[Smoke and Regression Procedure]] | CLI, CI, and post-deploy smoke checks. |
|
||||
| [[Testing Expansion Backlog]] | Gaps to cover before broader release confidence. |
|
||||
|
||||
@@ -33,6 +35,7 @@ seller, payment scanner, delivery, payout, dispute, and deployment behavior.
|
||||
| Smoke tests | Fast checks for one deployment target, usually via `BASE_URL`. | Backend scripts |
|
||||
| Browser E2E | Validate user-visible web flows. | Frontend Playwright |
|
||||
| Live dev E2E | Validate real dev deployment, CI image, scanner service, BSC Testnet, and test tokens. | QA/operator |
|
||||
| Concurrency profile | Ramp simultaneous full-flow workers and measure API, DB, scanner, notification, and chain behavior. | QA/operator + backend |
|
||||
| UAT | Validate product scenarios and acceptance criteria. | Product + QA |
|
||||
|
||||
## Golden Path Coverage
|
||||
@@ -47,7 +50,8 @@ The minimum live-dev confidence path is:
|
||||
6. Scanner confirms the token transfer.
|
||||
7. Seller delivers.
|
||||
8. Buyer confirms delivery.
|
||||
9. Flow pauses at the current product-policy boundary: release/grace/dispute automation is not complete.
|
||||
9. After every state-changing step, assert notifications for every expected recipient.
|
||||
10. Flow pauses at the current product-policy boundary: release/grace/dispute automation is not complete.
|
||||
|
||||
The current live tested version of this path is documented in
|
||||
[[Escrow Marketplace E2E Procedure#Reference execution - 2026-06-06]].
|
||||
@@ -70,4 +74,3 @@ The current live tested version of this path is documented in
|
||||
- Record enough evidence to reproduce a failure: request id, offer id, payment id, tx hash, chain id, token address, HTTP status, and CI build number.
|
||||
- Treat a passing local test as necessary but not sufficient for scanner/payment work. Payment changes must also be verified against dev after deploy.
|
||||
- Every live-dev test should state what remains untested or blocked.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user