While working on T177260: Rewrite disabled MobileFrontend browser tests to phpunit tests and Node.js browser tests, we discovered that there are differences between the Ruby automated browser testing stack (the "stack") and the Node.js stack and that this is slowing down the migration from the former to the latter. Moreover, we're not sure who owns creating these features.
Before we have that conversation, however, it'd be good to have a list of the features that haven't yet been ported to the Node.js stack.
- We have a list of features of the Ruby stack that haven't yet been ported to the Node.js stack.
- @Jdrewniak may have notes that he can share too.