Closed zenparsing closed 7 months ago
Discussed with @GeetaSarvadnya - Will divide the testing from https://github.com/brave/brave-core/pull/21926 on Windows and macOS as follows:
On Linux we can just do the regression testing of Uphold connection (existing account only, not new account) and tipping flows as mentioned via https://github.com/brave/brave-core/pull/21926.
Verified with
Brave | 1.64.90 Chromium: 122.0.6261.94 (Official Build) beta (x86_64)
-- | --
Revision | 726c6970a1e9c057c69d80e03ad95a7c561fbfe7
OS | macOS Version 13.6.4 (Build 22G513)
Note, confirmed with @zenparsing that the below (from the Connect flow) are hidden from logs, so if general regression testing is successful (connecting existing account, connecting new account, tipping, etc), then these can be considered working as expected:
GET https://api-sandbox.uphold.com/v0/me
(200)POST https://api-sandbox.uphold.com/v0/me/cards
(200) POST https://api-sandbox.uphold.com/oauth2/token
(202)Verified with
Brave | 1.64.91 Chromium: 122.0.6261.94 (Official Build) beta (64-bit) |
---|---|
Revision | 939586e20d208404b83713ea05cf5f6fa7fe3dd5 |
OS | Linux |
Per internal discussion only limited number of test cases were performed
Verification PASSED on
Brave | 1.64.104 Chromium: 123.0.6312.46 (Official Build) (64-bit)
-- | --
Revision | 0ca3d372cf8aab96fafdd75f5c5c8d2012bc0cc6
OS | Windows 10 Version 22H2 (Build 19045.4046)
As mentioned https://github.com/brave/brave-browser/issues/35834#issuecomment-1969228753 verified the following scenarios
Subtask of https://github.com/brave/brave-browser/issues/35542
Since Uphold will be updating their endpoints, we need to update our client implementation to accept any 2xx status code as successful.