Getting started

Preparation

Before you start writing any code, there are a few questions you should ask yourself about your product before getting started with TestBox.

1. What external services do you communicate with? Does your product send emails, for example? If so, do you have a way to block TestBox users from sending real emails? Consider any real-world implications of your product being used in a sandbox and plan to accomodate them.
2. Do you have any spam detection that might be triggered by your own automatic trial creation process?
3. Do you have a good understanding of all the processes that you must bypass in order to create an account automatically? For example: skipping email verification, bypassing CAPTCHA, etc?
4. Do you have a way to generate a bearer token, or something similar, in order to facilitate ingest sample data?
5. Are you responsible for your own authentication? Do you need to use a management API for something like Auth0 to create accounts?
6. Do you have any automated billing processes that need to be skipped or disabled for TestBox accounts?

Most customers are simply able to create a set of data models in their application and call it a day. However, if you have a more complex service-oriented architecture, outsource your authentication to a third party, or have other concerns, you may want to speak to a Partner Success Engineer at TestBox to talk through your solution before committing.

Things to know

• Does your application require an email address? You have choices! You can either use anything@example.com or anything@tbxofficial.com. However, you do not have any way of retrieving emails sent to these addresses, so plan accordingly.