-
Notifications
You must be signed in to change notification settings - Fork 4
test users
TODO
Also see /support-frontend/wiki/Test-users.
Currently test-user
s work using a special string (encrypted timestamp) held in the First Name field of the Identity user. During the first 48hours after the string is generated it points all/most of our systems to the UAT instances of Zuora & Salesforce, with the main use case being able to test PROD systems (typically UIs) but with test payment details (see Stripe, GoCardless and PayPal).
The current mechanism is a constant source of confusion and so would benefit from an overhaul - see wiki/Major-TODOs#overhaul-test-users-across-rr-to-become-identity-feature.
manage-frontend
itself doesn't have a test-user
s implementation, but instead relies on the X-Gu-Membership-Test-User
header from members-data-api
and it then uses this value to pass onto other APIs (see wiki/Proxying-API-Gateway-Lambdas) - this complexity could be avoided if test-users became an identity feature and was exposes as a flag in the existing Identity integration - see wiki/Major-TODOs#overhaul-test-users-across-rr-to-become-identity-feature
Not what you're looking for? Be sure to use the navigation sidebar on the right. ➡️