test(13): persist human verification items as UAT
This commit is contained in:
@@ -1,21 +1,14 @@
|
||||
---
|
||||
status: testing
|
||||
status: complete
|
||||
phase: 13-virtual-local-cloud-operations
|
||||
source: [13-VERIFICATION.md]
|
||||
started: 2026-06-23T00:00:00Z
|
||||
updated: 2026-06-23T00:00:00Z
|
||||
updated: 2026-06-23T12:00:00Z
|
||||
---
|
||||
|
||||
## Current Test
|
||||
|
||||
number: 1
|
||||
name: CONN-02 — Automatic provider OAuth token refresh during reconnect
|
||||
expected: |
|
||||
Triggering reconnect with an expired-but-refreshable OAuth token (no new_credentials
|
||||
in POST body) calls the provider's refresh endpoint and stores a new access_token.
|
||||
The test assertion is: decrypted credentials_enc after reconnect contains a new
|
||||
access_token that differs from the original.
|
||||
awaiting: user response
|
||||
[testing complete]
|
||||
|
||||
## Tests
|
||||
|
||||
@@ -26,15 +19,17 @@ expected: |
|
||||
(but still refreshable) OneDrive or Google Drive token. Inspect the decrypted
|
||||
credentials_enc — expect a new access_token from the provider, not a re-encrypted
|
||||
copy of the original.
|
||||
result: [pending]
|
||||
result: blocked
|
||||
blocked_by: third-party
|
||||
reason: "App not yet registered with OneDrive or Google Drive OAuth — no live provider credentials available to test the expired-token refresh path."
|
||||
|
||||
## Summary
|
||||
|
||||
total: 1
|
||||
passed: 0
|
||||
issues: 0
|
||||
pending: 1
|
||||
pending: 0
|
||||
skipped: 0
|
||||
blocked: 0
|
||||
blocked: 1
|
||||
|
||||
## Gaps
|
||||
|
||||
Reference in New Issue
Block a user