-
Notifications
You must be signed in to change notification settings - Fork 19
Summation of credentials testing attempts
Stephen Donner edited this page Jan 26, 2023
·
2 revisions
End-to-end testing (as much as possible) of purchasing, configuring, and using BraveVPN
, particularly credentialing (expiration
, cancellation
, renewal
)
NOTE: as of yet, none of the following attempts have confidently and reliably helped us test
account.bravesoftware.com
+VPN
button states, particularly their interplay together (SKU SDK, Guardian credentials, time-limited V2 credentials,Buy
/Log in
card, )
Full steps for each, below, are linked to in their refs section
[screenshot of Buy
/ Already logged in?
dialog]
refs:
- didn't work (for me, yet, but I need to retry); still successfully connects to
BraveVPN
(for an unspecified time - caching) - even after browser restart, still connected
[screenshot]
refs:
Attempt 3: client-side expires_at
and unblinded_creds
manipulations in Local State
(both manually and via shell scripts)
- still successfully connects to
BraveVPN
(for an unspecified time - caching)
[screenshot]
refs:
- only a single test - can we modify to also cover days 31, 32 of credentials?
[screenshot]
refs:
Ben set the expired_at
date to {today, yesterday} on the SKUs server backend
- credentials not expired on
account.bravesoftware.com
- still successfully connects to
BraveVPN
(for an unspecified time - caching) - won't scale / not self-service
[screenshot]
refs:
- tested via Slack PM with Ben, so no public log to point the team to, but he can resummarize the attempt, if need-be