Page MenuHomePhabricator

[Spike 8hrs] Document missing (?) features of the Node.js automated browser testing stack
Closed, ResolvedPublic

Description

Background

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.

Outcomes

  • We have a list of features of the Ruby stack that haven't yet been ported to the Node.js stack.

Notes

  1. @Jdrewniak may have notes that he can share too.

Event Timeline

I'm trying to keep T139740: Port Selenium tests from Ruby to Node.js updated (see TODO section at the top) with tasks that I am aware of.

phuedx moved this task from To Do to Doing on the Readers-Web-Kanbanana-Board-Old board.
phuedx added a subscriber: ovasileva.

^ Reflecting reality /cc @ovasileva (as we discussed during yesterday's standup).

ovasileva renamed this task from [Spike] Document missing (?) features of the Node.js automated browser testing stack to [Spike 8hrs] Document missing (?) features of the Node.js automated browser testing stack.Nov 28 2017, 5:42 PM
ovasileva triaged this task as High priority.

I've reviewed the mail and have left a little feedback.

OK. @Jdlrobson's initial notes are captured here and have been reviewed. I'll make sure that all of my comments are captured on the Flow board.

The next thing to do is to talk with Release-Engineering-Team about the pain points that we've identified.

I think I've captured my notes on the Flow board. Others should also feel free to do so.

Per our discussion at today's Sprint Kickoff - Reading Web meeting, I'm signing this off for now.