- Mentioned In
- T94150: Fix scenarios that fail at en.wikipedia.beta.wmflabs.org or do not run them daily
T95291: Fix browsertests for rank-, snaktype- and badge-selectors on SauceLabs
- Mentioned Here
- T106327: label normalization fails in Chrome / Opera / PhantomJS
T104330: ParseValue API module should optionally trigger validation
I made some progress in analysing the problem. It seems to occur because the browser window on SauceLabs gets resized during the testing session. When I start the tests on SauceLabs from my local machine the resize always happens at the beginning of the test. See:
When I run the same test on Jenkins and SauceLabs the resize happens in the middle of the test. See:
Note that the above use the old mediawiki_selenium gem. I also did some changes and experimented with mw_selenium 1.1.0. But still there was a resize in the middle of the process:
I contacted SauceLabs to discuss the issue a few weeks ago. Even a simple test, that is just calling a website triggers a resize.
This occurred with mediawiki selenium 1.1.0.
https://saucelabs.com/tests/21510b0e2bbc4edba5d6b504ddeddd6a (between 0:26 and 0:30)
Dylan from SauceLabs forwarded the issue to the images team to investigate on the 4th of May. Poked him again about it today.
currently chrome browser tests run well see
probably due to chrome issues with resizing see
Dylan from SauceLabs just wrote me a message:
"Our developers have deployed a fix to prevent this from happening; Can you check and let us know if it’s still a problem?"
So maybe they _really_ fixed it. Will run several test though.
Dylan answered again he reproduced the issue himself and they are looking for a solution.
"I’ve done some testing myself and it almost appears like Firefox doesn’t render or resize correctly for the first 30 seconds of tests, under Linux."
When looking at old screencasts on SauceLabs this is happening at least since mid March 2015. Sadly older screencasts are not available anymore. Does anyone remember screencast older than that with the described effect?
fails because of
fails because of
There are three non-flaky failing browser tests currently. They all pass locally against local instance for me.
- Edit sitelinks.Remove multiple sitelinks features/sitelinks.feature:204
- Creating statements.Cancel statement (outline example : | press the ESC key in the claim entity selector input field |) features/statement.feature:43
- Edit sitelinks.Edit sitelink features/sitelinks.feature:154