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
It seems that currently it is considered get practice to speficy translated field names/labels in the behat.yml file. Otherwise a simple login test will fail.
I guess, the login test could use the form ids instead of the labels, but I guess there is a preference for the labels.
I find this cumbersome and would like to propose the following: The functions that check the presence of strings should use the existing Drupal translations. This would make sure that tests aren't affected by translation changes and also not by a translation of a previously untranslated English term.
Does anybody have an opinion on the matter and/or suggestions for implementation?
The text was updated successfully, but these errors were encountered:
It seems that currently it is considered get practice to speficy translated field names/labels in the behat.yml file. Otherwise a simple login test will fail.
I guess, the login test could use the form ids instead of the labels, but I guess there is a preference for the labels.
I find this cumbersome and would like to propose the following: The functions that check the presence of strings should use the existing Drupal translations. This would make sure that tests aren't affected by translation changes and also not by a translation of a previously untranslated English term.
Does anybody have an opinion on the matter and/or suggestions for implementation?
The text was updated successfully, but these errors were encountered: