Selenium tests in Node.js project retrospective

I have been working on the project with more or less focus on it since 2015. Maybe the easiest way to follow the project is by taking a look at a few epic tasks:

T182421: Q3 Selenium framework improvements will come to an end in a few days, so last week a few of us had a meeting to discuss the project.

Conclusions:

  • The new Node.js Selenium framework is simpler and easier to use than previous Ruby framework.

What could have gone better:

  • A lot of effort is required to port large test suites. Some teams were able to do it, some teams were not.
  • It was not clear that both Ruby and Node.js frameworks could coexist.
  • It was not clear that Mocha is recommended, but not mandatory. It is still possible to write Cucumber tests.
  • Some features of the Ruby framework are not available in Node.js framework, like multi-user login.
  • Node.js's built-in assertion library sometimes doesn't provide useful error messages. Chai is a good alternative.
  • It would be better if a meeting like this happened at the beginning of the project, and several times during the project.

Things to do:

Meeting notes are available at 20180320 Selenium Retrospective.


Image by Paul Friel - Meerkat II, CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=24567063

Written by zeljkofilipin on Mar 26 2018, 2:28 PM.
Software Engineer (International contractor)
Projects
None
Subscribers
Aux0_8, hashar
Tokens
"Goat" token, awarded by Prtksxna."Barnstar" token, awarded by hashar.

Well done. Thanks for the retrospective.

Well,thanks for your sharing.