Patch ignored by phabricator
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/535610

I'm not sure why Phabricator is ignoring the other patch related to this task, but here it is:
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/535569

Assuming we are interested in knowing when a statement's value have been changed, here's what I was able to find so far:

• StatementChanger.js method save() has the object statement where the element claim (originates in Claim.js) lies.
• extensions/Wikibase/view/lib/wikibase-data-model/src/Claim.js contains the methods getClaim() and getMainSnak() but not a way to get the actual value entered. So we might want to start with adding that?

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.