No CI issues related to this test reported this week, resolving.

I'm really wondering what to do about this, since this test seemed to be failing relatively often on CI but for different reasons than it might be failing locally every once in a while (which it didn't always do but currently does). I think this needs some decision regarding whether it makes sense to test this in any other way (phpunit + Hamcrest) and is this scenario worth this sort of investment. would like opinions @alaa_wmde @WMDE-leszek @Ladsgroup @Rosalie_WMDE

I think it's best to leave it under test verification for a bit, to see if we get any ricochets from this being back on CI

@Tarrow @Lucas_Werkmeister_WMDE @Michael Thank you for your input. I think we'll keep this task in the JS scope for now and go with something similar to what we did in EntitySchema. A separate task will be opened to explore similar options for PHP linting.

T230481 might have an effect on this issue, stay tuned

@alaa_wmde I made a patch which could be abandoned in case we continue with the option of upgrading wdio.
The item pagepbject could also do with some cleaning up (mostly selectors which we ended up not using)

@alaa_wmde i'm fine with this, as a long standing solution seems to be less than obvious by now.

@Jdlrobson this test will be skipped till we've figured out what's going on there. Thanks for the heads up!

For lack of a better alternative and after much experimentation this patch was merged although the browser.pause()method is being used in it. Leaving this here in case future flakiness leads back to this task.

@alaa_wmde this can go to the To Do column again, can't it?

Awesome. Thanks @Addshore !

@Daimona unfortunately requiring phan config 0.6.1 in composer.json did not seem to have an effect.

It now should be testable in beta cluster, right?

of course #facepalm . How do we check logs on Beta cluster?

+++ Steps to verify +++

@Niedzielski Yes. it's not that we are unable to encounter any error, more like our normal Ruby browser tests setup does not work in case of Minerva and we cannot get any Ruby tests running.

We are having difficulties with reproducing it locally (just with Minerva, Ruby tests for other extensions do run locally) could anyone advise regarding the setup you use for it? (Maybe @pmiazga or @Niedzielski ?)

As EntitySchema is already deployed, this can be closed.