If the feature or scenario requires custom browser configuration, it should be tagged @custom-browser. This convention is currently not used. At the moment we tag features or scenarios that need custom browser configuration with @language tag in UniversalLanguageSelector repository and with @user_agent tag in MobileFrontend repository.
https://www.mediawiki.org/wiki/Manual:Coding_conventions/Selenium#Optional_tags
Version: wmf-deployment
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T62335 Implement Ruby/Selenium/Cucumber/page-object coding conventions | |||
| Resolved | zeljkofilipin | T63458 Add support for @custom-browser Cucumber tag to mediawiki_selenium Ruby gem |
Change 113769 had a related patch set uploaded by Zfilipin:
Added support for @custom-browser Cucumber tag
Change 113776 had a related patch set uploaded by Zfilipin:
Using @custom-browser Cucumber tag instead of @user_agent
Change 113780 had a related patch set uploaded by Zfilipin:
Simplified code when using @custom-browser Cucumber tag
Change 113785 had a related patch set uploaded by Zfilipin:
Using @custom-browser Cucumber tag instead of @user_agent
Change 113780 merged by jenkins-bot:
Simplified code when using @custom-browser Cucumber tag
Change 113776 merged by jenkins-bot:
Using @custom-browser Cucumber tag instead of @user_agent
Change 113785 merged by jenkins-bot:
Using @custom-browser Cucumber tag instead of @user_agent