Topic on User talk:Jdlrobson/Experiences porting Ruby browser tests to NodeJs

I really did not think running tests is not so much more complicated that before. It's just two commands. We could create scripts in package.json to make it easier.

Please keep in mind that only one person is working on Selenium framework. Because of that we (my team, not royal "we") have decided to support only two environments. MediaWiki-Vagrant and Jenkins. The assumption is that if people prefer a custom environment they will be experienced enough to be able to make adjustments to Selenium framework to make it work for their environment.

In node development, the expectation I have is that I can run `npm run selenium` to run tests. Previously we used `bundle exec` which would be the Node equivalent.

Because that is not possible, I have to read documentation. I do this every time I need to troubleshoot tests as it's difficult to remember how to run them.

It's definitely something I can live with, but it is something I miss about the old stack. I feel like it should be possible to get `npm run selenium` I just haven't had an opportunity to investigate that yet.

Please keep in mind that Ruby and Node frameworks are similar, but not identical. Some things possible/available in one are not possible/available in the other.

Also, how to run tests is documented in readme files (core, Popups, RelatedArticles)...

That said, I agree that running tests should be as easy as possible. I have created T182691 so I don't forget about it.