In T219920 given our browser tests disappeared we prioritised getting them running again.
With the dust settled on that urgency we should consider what changes are needed to bring consistency to the browser tests compared to other extensions.
- Do we still want to use cucumber long term? if so what is the motivation ?
- if not, let's remove the feature files inside the new tests. What improvements can be made to the browser tests that promote readability but also reusability. How best to strike a balance between the two?
I suggest we meet and chat through the code and existing patterns and find a compromise we are happy with.