While working on T160238, I propose we split into groups for maximum effectiveness.
This task deals with the QuickSurveys extension.
* Feature: Survey bucketing (opting in)
** Scenario: Internal survey is visible when bucketed # tests/browser/features/bucketing.feature:14
** Scenario: External survey is visible when bucketed # tests/browser/features/bucketing.feature:22
* Feature: External surveys
** Scenario: External survey is visible with flag #
** Scenario: External survey is not present without flag when not bucketed
** Scenario: External survey is not present when dismissed # tests/browser/features/external_survey.feature:21
** Scenario: User can participate in external survey # tests/browser/features/external_survey.feature:27
* Feature: Integration
** Scenario: Survey is visible with quicksurvey=true flag # tests/browser/features/integration.feature:6
* Feature: Internal surveys
** Scenario: Internal survey has multiple answers #
** Scenario: Internal survey is visible with flag #
** Scenario: Internal survey is not present without flag
** Scenario: Internal survey is not present when dismissed # tests/browser/features/internal_survey.feature:24
** Scenario: User can participate in internal survey # tests/browser/features/internal_survey.feature:30
== Notes
1. The `mw-wdio-nodepool` builder replaces the `mwext-ruby-jessie` builder in [[ https://github.com/wikimedia/integration-config/blob/49e7ef9f9442ace863fab786a9fbcd9bcf93e032/zuul/layout.yaml#L5168 | integration-config/zuul/layout.yaml ]], which will make `check experimental` run the new WebdriverIO-based tests.
2. Put your new tests in the `tests/selenium/`, following [[ https://github.com/wikimedia/mediawiki-extensions-RelatedArticles/tree/f4708684af88f1d5a4e28353d28e4837c46b10cc/tests/selenium | the example structure in RelatedArticles ]].