On the beta cluster, the tests are run using "Selenium user" account.
There is a test which assumes the user's page is blank which is now
failing as a result of this edit:
https://en.m.wikipedia.beta.wmflabs.org/w/index.php?title=User:Selenium_user&oldid=371028
Test is now disabled there but will still run on commits via the
@integration tag.
Additional change:
* Drop the additional @login tag
Change-Id: Ie116caed32883c58edfa2ab3dfa47bbbefdd6f31
These flake too much. We have coverage in @firefox or @integration
so let's remove these test runs from the beta cluster job.
All tests will run somewhere.
Bug: T170890
Change-Id: I269991a22ab5a2b54aed8ad453013bb9be648502
If mediawiki.notification has loaded that should be enough to assume
the toast is ready to have its text checked.
Change-Id: Ic546877eae0ea6dd59dbf88bf9267bcd1957f779
These are failing consistently due to T172835. Let's not run it in the
@chrome job and just rely on the Firefox coverage. We'll keep one test
in @chrome as it runs in integration mode (per commit).
Change-Id: Ic417148574208389b66249b2d98e009beef70fa2
It seems trying to test both the steps can cause
false positives. Relaxing these checks seems to make
our Jenkins job happy without breaking the tests themselves
Change-Id: I119111e97f23d2f0dac7cbb0e5b86c1df0562598
Changes:
* Use css rather than class for finding toast
* Correct a test typo
* Add a step to wait until the mediawiki.notification module
has been loaded
Bug: T170890
Change-Id: I86e48e00ebb83772149da7c7f20097b5436a0cf5
Copies approach for the text of the first heading should be
accounting for the fact that the toast can have an empty
message "" at any given time.
Bug: T170890
Change-Id: Iba8a503a2aea30cb46fba27f000843183e9c46f1
A toast autohides within 5 seconds and its display properties are
inherited from #mw-notification-area. This slight tweak waits for
mw-notification-area to be visible before verifying toast and its
contents
Change-Id: I89beaf9d131155e958cc9aae84a9e30ffd8e9e4f
Introduces a new generic
"I should see a toast with message ".*""
step reducing toast steps to two generic ones.
Change-Id: Ic8b91c78f6df088244f15223ee4ed658847a05b5
Changes:
* Update docs
* Update browser test artifacts
* Update comments
* Update phpunit test groups
* Update phpunit test namespace
* Update `die` when MobileFrontend not installed
* Remove the migrate script which is no longer needed
Change-Id: I83432b3f7f0bcd07ed08259972b8ff89147104b6
Sniffs that are currently failing are disabled in phpcs.xml.
Additional changes:
* Fix problem in test file
Change-Id: I53642e9d7bc1ef96e359cfe04a8f93dabbc977eb
Test scenario for getContextSpecificModules() mocks only Skin->getTitle()
behavior, but while executing isAllowedPageAction() Skin will create a
UserPageHelper with default RequestContext. As RequestContext is not mocked,
$context->getTitle() will return undefined what could lead to tests crash
Changes:
- instead of mocking SkinMinerva::getTitle() pass test context with injected
title. Other tests will work properly as MediaWikiTestCase::tearDown() always
restes RequestContext to default
Bug: T170624
Change-Id: I872fddf8d9c52a6875bb6c69a12407a8125fba4c
This is programmatic output from python3 scripts/migrate.py
This will result in a Minerva skin dependent on MobileFrontend.
Post merge we will rename message keys to have minerva- prefix
Bug: T166748
Change-Id: Iff1f7e63e796cc5d4a6d2ab0370e0c33248d2fce
This moves all browser tests from MobileFrontend to the Minerva repo
in preparation for separating the two.
Note, this means browser tests will exist in both repositories for a
period of time. This is important and necessary to ensure we do not
break anything.
See:
https://lists.wikimedia.org/pipermail/mobile-l/2017-July/010536.html
Bug: T168758
Change-Id: I84ae3ea14191f672cabcd52020e80b0a40a72ce1
