Skip to content
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

Merged
merged 2 commits into from
Feb 17, 2023
Merged

feat: Adds Testing page #77

merged 2 commits into from
Feb 17, 2023

Conversation

dhudec
Copy link
Contributor

@dhudec dhudec commented Feb 16, 2023

Description

  • Documents testing recommendations
  • Documents test card numbers

Testing required outside of automated testing?

  • Not Applicable

Screenshots (if appropriate):

  • Not Applicable

Rollback / Rollforward Procedure

  • Roll Forward
  • Roll Back

Reviewer Checklist

  • Description of Change
  • Description of outside testing if applicable.
  • Description of Roll Forward / Backward Procedure
  • Documentation updated for Change

@vercel
Copy link

vercel bot commented Feb 16, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
developers-basistheory-com ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Feb 17, 2023 at 3:22PM (UTC)

@dhudec dhudec marked this pull request as ready for review February 17, 2023 15:33
@dhudec dhudec requested a review from a team as a code owner February 17, 2023 15:33
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this to needed?

Copy link
Contributor Author

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about proxies?

Copy link
Contributor Author

@dhudec dhudec Feb 17, 2023

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.

@dhudec dhudec merged commit 04e92b1 into master Feb 17, 2023
@dhudec dhudec deleted the eng-4248 branch February 17, 2023 19:23
bt-platform-eng pushed a commit that referenced this pull request Feb 17, 2023
# [1.29.0](v1.28.1...v1.29.0) (2023-02-17)

### Features

* Adds Testing page ([#77](#77)) ([04e92b1](04e92b1))
@bt-platform-eng
Copy link

🎉 This PR is included in version 1.29.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants