-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Adds Testing page #77
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dedicated Basis Theory [tenant](/docs/concepts/access-controls#what-are-tenants) for each | ||
test environment that is separate from your production tenant. For example, if you maintain a separate Development, | ||
QA, Staging, and Production environment for your systems, we recommend that you mirror this setup by creating 4 separate tenants in Basis Theory. | ||
This can help you to isolate test data from production data and allow you to more securely lock down access to production API keys. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this to
needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
either way is correct
QA, Staging, and Production environment for your systems, we recommend that you mirror this setup by creating 4 separate tenants in Basis Theory. | ||
This can help you to isolate test data from production data and allow you to more securely lock down access to production API keys. | ||
|
||
## Testing Reactors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about proxies?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Scope creep! I don't have time to write about testing proxies too. All of this was extra and unplaned as it is.
# [1.29.0](v1.28.1...v1.29.0) (2023-02-17) ### Features * Adds Testing page ([#77](#77)) ([04e92b1](04e92b1))
🎉 This PR is included in version 1.29.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
Testing required outside of automated testing?
Screenshots (if appropriate):
Rollback / Rollforward Procedure
Reviewer Checklist