In T162256#3177090, @Jdlrobson wrote:

I've updated patch to use the library. I forgot how to test locally so I haven't been able to verify it works. Feedback welcomed!

Documented at Selenium/Node.js. There is entire Run tests section! :)

Is there any easier way to run selenium tests locally than executing browser tests from the core directory? Ideally I'd want a one line command e.g. npm run browsertests to make it easier to write tests.

You have to run tests from mediawiki/core directory. To run all tests: npm run selenium

@zeljkofilipin - I can't work out how to run these browser tests within Jenkins check experimental doesn't seem to work.. where do they show up?

@Jdlrobson apologies, we have made some changes to the CI recently and I have forgot to update the documentation:

https://www.mediawiki.org/wiki/Selenium/Node.js/mediawiki-core-qunit-selenium-jessie_Jenkins_job

I am working on it (T164002: Update documentation for mediawiki-core-qunit-selenium-jessie Jenkins job).

I will port one test per repository and make sure it runs in CI.

In T162256#3402689, @Jdlrobson wrote:

Blocked on T164002 which is blocked on T164721

Both tasks have been resolved. 🎉

After T164024 is done, we'll need to work out what to do next and when and how we'll do it.

@zeljkofilipin are there any guidelines on how to login in a browser test? I can't find any examples.

@Jdlrobson there is a [[ https://phabricator.wikimedia.org/source/mediawiki/browse/master/tests/selenium/specs/user.js;ca01c9ff7f62556f76bba61cad4cfbcbc9519828$34-47 | User should be able to log in ]] test in core! 😉

 it( 'should be able to log in', function () {

   // create
   browser.call( function () {
     return CreateAccountPage.apiCreateAccount( username, password );
   } );

   // log in
   UserLoginPage.login( username, password );

   // check
   assert.equal( UserLoginPage.userPage.getText(), username );

} );

So, from an extension:

const UserLoginPage = require( '../../../../../tests/selenium/userlogin.page' );
UserLoginPage.login( username, password );

username and password are defined in wdio.conf.js.

const UserLoginPage = require( '../../../../../tests/selenium/userlogin.page' );
UserLoginPage.login( username, password );

great that was what I was looking for.

Just removing our -kanban board, let us know if you need help on the sub-tasks.

Change 384041 had a related patch set uploaded (by Zfilipin; owner: Jdlrobson):
[integration/config@master] Run Selenium tests for Reading Web extension

https://gerrit.wikimedia.org/r/384041

Change 384041 merged by jenkins-bot:
[integration/config@master] Run Selenium tests for Reading Web extension

https://gerrit.wikimedia.org/r/384041

@Jdlrobson, is this a good candidate to discuss for inclusion in the next sprint?

Change 502907 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
[mediawiki/extensions/MobileFrontend@master] Migrate browser tests from Ruby to Node.js

https://gerrit.wikimedia.org/r/502907

Blocked on T199939