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
Is anyone using the Behat Drupal Extension to test multi-lingual sites using the domain as the language selection method? How did you approach it?
Up until our, our multi-lingual site detected language based on path, but we now have to change to domain based detection. Our existing test suite works fine with path-based detection, but now we need to update it to work with domain-based.
I am wondering how best to approach it, specifically:
base_url in behat.yml - set this to the default language?
testing language toggles work - currently we follow the toggle link and use 'And I should be on "es/some-page"' but this will need to be updated to check the domain has changed. Should we just make the URLs absolute, or is there a nicer way? If we had to make them absolute then we'd need to use a variable, as the domains are different depending on whether we're running the tests locally, on dev, or on staging.
tests that log in, do something, then change to a different language. Currently these work fine as the user remains logged in after the language change, because they stay on the same domain and the cookie is still set. However with domain based language, going to another language will mean you are not logged in on that site, so how do we get Behat to log us in to the new domain?
Any thoughts appreciated.
The text was updated successfully, but these errors were encountered:
Is anyone using the Behat Drupal Extension to test multi-lingual sites using the domain as the language selection method? How did you approach it?
Up until our, our multi-lingual site detected language based on path, but we now have to change to domain based detection. Our existing test suite works fine with path-based detection, but now we need to update it to work with domain-based.
I am wondering how best to approach it, specifically:
Any thoughts appreciated.
The text was updated successfully, but these errors were encountered: