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
Regression testing depends on a bunch of ENV vars to get things configured: account, password, provision mode, libraries and so on. As the list of vars expanded, it has become hard to manage and modify them. Also, there is no centralizedand easy way to get "teting profiles" config files.
It might be a good idea to remove dependency on ENV vars introducing a special service with the following logic:
look for ENV vars
if there is a local YAML file - use override from YAML file
That way we would be able to easily create, edit and share config ENV for regression testing.
The text was updated successfully, but these errors were encountered:
Regression testing depends on a bunch of ENV vars to get things configured: account, password, provision mode, libraries and so on. As the list of vars expanded, it has become hard to manage and modify them. Also, there is no centralizedand easy way to get "teting profiles" config files.
It might be a good idea to remove dependency on ENV vars introducing a special service with the following logic:
That way we would be able to easily create, edit and share config ENV for regression testing.
The text was updated successfully, but these errors were encountered: