Testing Your Auth0 Implementation
We recommend that you run unit and integration tests for your Auth0 implementation prior to go-live. For your tests, we recommend that you mock the Auth0 APIs. We do not allow the Auth0 APIs to be used for testing purposes, and such actions may lead to your account being rate limited (especially if you're creating and deleting test users at a high rate during a short period of time).
When conducting performance testing, you may encounter issues with your implementation. The following are steps you can take to begin the troubleshooting process and identify where there might be issues of concern.
The Auth0 Dashboard
The Logs section of the Auth0 Dashboard stores data on:
- Actions taken in the Dashboard by administrators
- Authentications made by your users
There are also extensions that you can use for logging purposes, including exporting logs to third-party tools and gathering information on the use of custom code in your account.
Third-Party Testing Tools
There are a number of third-party testing tools that you can use for performance testing against RESTful APIs. Here are some options you might consider (note that Auth0 does not endorse any particular product or tool):
These tools should provide activity logs that help you identify anything that is concerning. If you need assistance with deciphering your log or identifying the potential issue, please contact Support.
If you discover an issue that you can reproduce, you can create a HAR file and send it to our Support team for additional assistance.
Testing Rules and Custom Database Connections
The auth0-rules-testharness package provides an easy way to deploy, execute, and test the output of Auth0 Rules using a real webtask sandbox environment.
The auth0-custom-db-testharness package provides an easy way to deploy, execute, and test the output of Auth0 Custom DB Scripts using a real webtask sandbox environment.