T180228: Port Wikibase Selenium tests from Ruby to Node.js has a long list of Ruby browser tests that we want to port. Figure out if this can be grouped in a sensible way (e. g. port tests X first, then tests Y, etc.) and if any tests don’t need to be ported at all.
|Open||None||T139740 Port Selenium tests from Ruby to Node.js|
|Open||None||T180451 Port Selenium tests from Ruby to Node.js for WMDE Engineering repositories|
|Open||None||T180228 Port Wikibase Selenium tests from Ruby to Node.js|
|Resolved||Michael||T221638 Investigate how to port Wikibase Selenium tests from Ruby to Node.js|
Below are the groups I've found. I would suggest starting with the first group, possibly with a subtask for each of the feature files.
I see one subgroup about 'Termbox editing':
- label.feature (6 scenarios of which 4 are parameterized)
- description.feature (6 scenarios of which 4 are parameterized)
- aliases.feature (17 scenarios of which 4 are parameterized)
- header.feature (6 scenarios of which 2 are parameterized)
- empty_label_and_description.feature (8 scenarios of which none are parameterized)
Then there is a group of three tiny tests with a small single scenario each:
There are the two smoke tests which are somewhat cross-cutting:
There are the two about sitelinks:
- sitelinks.feature (16 scenarios)
- sitelinks_badge.feature ( 5 scenarios)
There is the long list of statement tests.
Lastly there are three that appear to be not part of any other group:
- reference.feature (12 scenarios of which 2 are parameterized)
- special_set_label.feature (7 scenarios)
- authority_control_gadget.feature (1 parameterized scenario)
The person working on these task should decide which scenarios have to actually be implemented and which are obsolete or redundant with already existing tests.