For advanced Test Environment management capabilities, please check our Integration with Apwide Golive.
- Don't create hundreds or thousands of Test Environments as it will harden their usage and add some performance overheadDon’t make composed environment names, such as ”<os>_<browser>_<stage>” as it will pollute the environment namespace and harden management
- Don't try to do data-driven testing using Test Environments; they're not tailored for that
Besides other usage issues, if you have a large number of environments (>100>500), it will impact the calculations that need to be done and the size of the Lucene index.
Please try to have a limited, restricted, and well-defined list of Test Environments.