This article outlines best practices for testing new features or integrations without disrupting the experience of your end users
Why Use a Separate Testing Environment?
Testing in a controlled environment ensures that you can experiment with new features safely and users in your institution's live environment will not be affected by test configurations.
Two Lean Library Environments
As an admin, you have access to two distinct Lean Library environments:
1. Beta Environment
URL: https://beta2.leanlibrary.com/
-
Used for early access to new features.
-
Ideal for short-term testing and configuration experiments.
-
Fully replicates the live environment in terms of technology and data.
2. Live (Production) Environment
URL: https://app2.leanlibrary.com/
-
The environment your end users access.
-
All production-ready configurations should be applied here.
Key Differences Between Beta and Live
-
Data Separation: Changes made in Beta do not affect the Live environment.
-
Independent Databases: Each environment operates on a distinct database.
How to Access the Beta Environment
To access the Beta environment:
- Log in via https://beta2.leanlibrary.com/ using the same credentials as your live environment. You can always use the Forgot Password option if you can not remember your credentials.
-
If you still don't have access, send an email to support@leanlibrary.com to request a Beta admin account.
-
Once you receive your account activation email, log in via https://beta2.leanlibrary.com/.
You must use the Beta browser extension to see the impact of changes made in the Beta dashboard. Click here to download the extension.
Tip: Temporarily disable your Live extension to avoid any confusion while you are testing on Beta.
When You're Ready to Go Live
Once you’ve completed testing:
-
Log in to https://app2.leanlibrary.com/.
-
Reapply the successful configurations from Beta into the Production environment.
If you have questions about testing or need additional support, please contact us at support@leanlibrary.com.