The test was failing because a popup was added to the beta cluster.
Popup text:
Download a browser extension to get new features and help us improve Wikipedia
Bug: T270771
Change-Id: I6ba0026fcaa05610d4a310605f5ff6ae93705bc0
Assertions from Expect library are more readable that assertions from Assert library.
Bug: T325740
Change-Id: I686f39d7ef08085037bc34219c6f55eba9da8dd1
This piece of code is used in two tests in user.js.
It makes sense to extract it to a page object.
Bug: T325740
Change-Id: Iedc8108080f295cf124953dba1f237f08957aba4
Three tests with that name were by mistake going to `/Main Page` instead of `Main Page`.
Bug: T373125
Change-Id: I5936f2c944765f576ab87d899002f7f24116ef44
Make it explicit that there are three separate tests
by expanding test names.
Until now, these three tests were doing the same thing,
but in a different way. All three tests had the same name.
That made it harder to debug if anything went wrong.
For example, all three tests created the screenshot file
with the same name.
Bug: T373125
Change-Id: I53f62186fd4e8ffbe5e93642c933da2493b91896
Why:
- When signing up for an account, temporary users are currently forced
to provide a reason for creating an account, and also have the option
to send a temporary password to an email address.
- Neither of these options are useful for temporary users wanting to
create a full user account.
What:
- Don't show these two form fields on Special:CreateAccount for temporary users.
- Add a functional test for the temporary user account creation flow.
Bug: T328718
Change-Id: Ie545857f7647be89d9462ec2b0def48690f0a2bf
Why:
- In WDIO < 9, the function to be run by browser.execute() must be
synchronous.[1] Asynchronous code should be run via executeAsync()
instead.[2]
- isTargetNotWikitext() however runs asynchronous code via execute(),
which may be interfering with tests.
What:
- Have isTargetNotWikitext() use executeAsync() instead.
[1] https://v7.webdriver.io/docs/api/browser/execute/
[2] https://v7.webdriver.io/docs/api/browser/executeAsync/
Change-Id: I05aaf8d89c5b52ffc94f70a4f887a98a99037027
Without this, it’s possible (though rare) for two tests to write to the
same file, producing garbled XML. As far as I can tell, there’s no way
to access the test name in the outputFileFormat callback (it gets passed
an options object but the test name doesn’t seem to be included in it),
so just add a random string, using the simplest method that should work
in every JS engine. (I tried using crypto.getRandomValues() first, and
it works without warning in fresh-node18, but ESLint still yelled at me
about the Node.js feature being experimental.)
As far as I can tell from Codesearch [1], the file names are matched by
Jenkins using the glob log/WDIO.xunit*.xml, so the changed file name
pattern should still work there.
[1]: https://codesearch.wmcloud.org/search/?q=WDIO%5C.xunit
Bug: T307914
Change-Id: If51549f1318c601782b3fa4ff34923e5c7db5e62
This reverts commit 4ef806b6e3.
Reason for revert: This is still a fundamental bug in the test runner that
has blocked us being able to run browser tests for WikiLambda for over a year.
Bug: T358530
Change-Id: I77104fac7d190267e40895b9e66732ff6f9c0dc7
This reverts commit 83f65121f8.
Depends-On: I0ceace61899d0b1bd047e5011acaddd4428c944e
Reason for revert: Try and get to the bottom of the problem here.
Change-Id: I65b9f5a2bcd27415b61cd56f35f096d3bb2b1145
Currently, we're not entirely sure why but this test is failing
consistently on patches that seem unrelated - skip it for now while we
investigate what is causing it to fail so that merges are unblocked
Bug: T369872
Change-Id: I1c8115e95749bcb5e6b55d0ebe31267178042783
"User should be able to log in" is failing.
Don't run it in the daily job until we figure out what's wrong.
Bug: T270771
Change-Id: I72c524eba700e8d100435d3365dbfc4ed934bb7b
This commit adds missing async defintions in a couple of
methods for our wdio page tests. It's better to define the
functions so that its clear that its async.
Bug: T358092
Change-Id: I9006deb9a9a0bb524ab61a16c6f41621482f21bf
