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
Howitzer uses page object pattern. We do not need to specify protocol and host for each page class. Howitzer gets settings from default.yml (with prefix app_) and set hosts automatically. It works perfectly, until you do not need to test application with different domains. For that reason, howitzer provides site dsl method.
In real life you deal with different environments and it is very important to keep the data as configurable. As a simple case, we could add new setting in default.yml
Much better now, but what about ability to change it to https for example for staging environment and keep http for development one. Should not be a problem.
Howitzer uses page object pattern. We do not need to specify protocol and host for each page class. Howitzer gets settings from default.yml (with prefix
app_
) and set hosts automatically. It works perfectly, until you do not need to test application with different domains. For that reason, howitzer providessite
dsl method.In real life you deal with different environments and it is very important to keep the data as configurable. As a simple case, we could add new setting in default.yml
and then
Much better now, but what about ability to change it to https for example for staging environment and keep http for development one. Should not be a problem.
Ok, what about using basic authentication? Following code will work, but in some cases we need url without login and password in URL
Then we could keep url parts separately and use addressable gem:
Huh, too big amount of code to deal with 1 additional url, is not it?
We need to find an approach how to simplify it. For example,
The text was updated successfully, but these errors were encountered: