You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reduce confusion lets rename the public test environemets to demo. This way if we talk about test env we always mean the environemnts for automated testing and demo is the publicly available environment for pre-production testing, practice and feature reviews
The text was updated successfully, but these errors were encountered:
Actually I strongly advise against it.
That's a common naming practice in rails applications.
Renaming test envirnonent might not only confuse future app developers alot, but also may break not just our app, - it might break any of the used gems (since they could have checks involving current environment). Than could have bigger impact and be more confusing then simple renaming of Git branches from master to main for the sake of BLM/SJW.
I think it might be wisier to use public test or pre-production term to the public test environment.
well i must admins its strange choice to use such an ambiguous naming for automated testing environments,. So we will flip the task the other way around and rename our own public test to something like demo or pre-production. thank you for your feedback @yulgolem
vohmar
changed the title
Rename the env for running automated tests
Rename the public test environments
Nov 24, 2021
To reduce confusion lets rename the public test environemets to demo. This way if we talk about test env we always mean the environemnts for automated testing and demo is the publicly available environment for pre-production testing, practice and feature reviews
The text was updated successfully, but these errors were encountered: