Hi Greg,
actually I'm more interested in creating the coverage reports on a local dev box in the context of extension development / local CI (checking the coverage of newly created JS tests). I did find info about running JS tests but little to nothing about coverage. Maybe I missed something.
/Alexander
Am 27.10.2021 um 01:37 schrieb Greg Grossmeier:
> On Tue, Oct 26, 2021 at 2:31 AM planetenxin <planetenxin(a)web.de <mailto:planetenxin@web.de>> wrote:
>
> Is there a generic approach, how to get some coverage reports for the JavaScript parts of MW and MW extensions?
>
>
> Is https://doc.wikimedia.org/cover/ <https://doc.wikimedia.org/cover/> helpful in your case?
>
> --
> | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
Hi,
I am trying to run selenium test suite for EntitySchema extension. I have followed this
https://www.mediawiki.org/wiki/MediaWiki-Docker/Extension/Popups. Some of the test cases
are getting failed.
Logs:
$ npm run selenium-test
> selenium-test
> wdio tests/selenium/wdio.conf.js
Execution of 5 spec files started at 2021-10-27T21:45:50.128Z
[0-0] RUNNING in chrome - /tests/selenium/specs/editSchema.js
[0-0] Error in "Schema Edit Page.given that a user is allowed.returns to schema view page on submit"
Error: element (".entityschema-label") still not displayed after 5000ms
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at ViewSchemaPage.getId (/media/saad/sda9/Outreachy-2021-Dec/Wikimedia/mediawiki/extensions/EntitySchema/tests/selenium/pageobjects/view.schema.page.js:66:56)
at Context.<anonymous> (/media/saad/sda9/Outreachy-2021-Dec/Wikimedia/mediawiki/extensions/EntitySchema/tests/selenium/specs/editSchema.js:44:19)
[0-0] FAILED in chrome - /tests/selenium/specs/editSchema.js
[0-1] RUNNING in chrome - /tests/selenium/specs/helloworld.js
[0-1] PASSED in chrome - /tests/selenium/specs/helloworld.js
[0-2] RUNNING in chrome - /tests/selenium/specs/special/new.js
[0-2] PASSED in chrome - /tests/selenium/specs/special/new.js
[0-3] RUNNING in chrome - /tests/selenium/specs/special/setEntitySchemaLabelDescriptionAliases.js
[0-3] Error in "SetEntitySchemaLabelDescriptionAliasesPage:Page.is possible to edit Schema identifying information"
Error: element (".entityschema-description[lang=en]") still not existing after 5000ms
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at ViewSchemaPage.getDescription (/media/saad/sda9/Outreachy-2021-Dec/Wikimedia/mediawiki/extensions/EntitySchema/tests/selenium/pageobjects/view.schema.page.js:33:85)
at Context.<anonymous> (/media/saad/sda9/Outreachy-2021-Dec/Wikimedia/mediawiki/extensions/EntitySchema/tests/selenium/specs/special/setEntitySchemaLabelDescriptionAliases.js:48:38)
[0-3] Error in "SetEntitySchemaLabelDescriptionAliasesPage:Page.is possible to edit Schema in another language"
Error: element (".entityschema-description[lang=de]") still not existing after 5000ms
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at ViewSchemaPage.getDescription (/media/saad/sda9/Outreachy-2021-Dec/Wikimedia/mediawiki/extensions/EntitySchema/tests/selenium/pageobjects/view.schema.page.js:33:85)
at Context.<anonymous> (/media/saad/sda9/Outreachy-2021-Dec/Wikimedia/mediawiki/extensions/EntitySchema/tests/selenium/specs/special/setEntitySchemaLabelDescriptionAliases.js:64:38)
[0-3] FAILED in chrome - /tests/selenium/specs/special/setEntitySchemaLabelDescriptionAliases.js
[0-4] RUNNING in chrome - /tests/selenium/specs/viewSchema.js
[0-4] PASSED in chrome - /tests/selenium/specs/viewSchema.js
"dot" Reporter:
..F..............FF...
Spec Files: 3 passed, 2 failed, 5 total (100% completed) in 00:01:14
Any dependencies that I need to add? Any leads would be helpful.
#selenium #EntitySchema #extensions #testsuite #testcases
Hi,
I've been searching quite a bit on MediaWiki.org but I can't find how
to tell the VisualEditor to stop saving and (especially) recovering
changes that I haven't explicitly saved. Is there a method?
Thanks,
Strainu
Hi,
Suppose I have an extension that utilizes SearchIndexFieldsHook and
SearchDataForIndexHook to add a novel field, called 'more_file_text',
to the indexed data for pages. This new field is of INDEX_TYPE_TEXT.
Via those two hooks, I've managed to get data for this field stored in the
elasticsearch index. But... how do I get CirrusSearch to actually include
this field in its searches?
It would be a-ok if the 'more_file_text' could just be treated as additional
content for the 'file_text' field. (However, simply populating the existing
'file_text' field via the SearchDataForIndexHook does not work, because the
FileContentHandler::getDataForSearchIndex() method runs after the hook and
always forcefully overwrites the 'file_text' field.)
Will any existing CirrusSearch hooks or configuration parameters allow me
to achieve this?
(And/or, is there a better forum for me to ask this question?)
-mm
Hi,
I am trying to run selenium test suite for Popups extension. I have followed this https://www.mediawiki.org/wiki/MediaWiki-Docker/Extension/Popups. Some of the test cases are getting failed.
[0-0] RUNNING in chrome - /tests/selenium/specs/page_previews.js
[0-0] AssertionError [ERR_ASSERTION] in "Dwelling on a valid page link I should see a page preview"
AssertionError [ERR_ASSERTION]: Page preview is shown.
at Context.<anonymous> (/core/extensions/Popups/tests/selenium/specs/page_previews.js:18:3)
[0-0] AssertionError [ERR_ASSERTION] in "Dwelling on a valid page link Quickly hovering, abandoning and re-hovering a link shows page preview"
AssertionError [ERR_ASSERTION]: Page preview is shown.
at Context.<anonymous> (/core/extensions/Popups/tests/selenium/specs/page_previews.js:31:3)
[0-0] FAILED in chrome - /tests/selenium/specs/page_previews.js
[0-1] (node:6255) ExperimentalWarning: The dns.promises API is experimental
[0-1] (node:6255) ExperimentalWarning: The fs.promises API is experimental
[0-1] RUNNING in chrome - /tests/selenium/specs/reference_previews.js
[0-1] PASSED in chrome - /tests/selenium/specs/reference_previews.js
"dot" Reporter:
F.F....
Spec Files: 1 passed, 1 failed, 2 total (100% completed) in 00:00:55
Any dependencies that I need to add?
#selenium #Popups #extensions #testsuite #testcases
[1] describes how to do QUnit testing but it does not mention if / how to get some coverage reports (e.g. with the help of Istanbul). While searching for an answer, I found this [2] post about testing challenges for Extension:Popups and solutions implemented for this specific extension.
Is there a generic approach, how to get some coverage reports for the JavaScript parts of MW and MW extensions?
/Alexander
[1] https://www.mediawiki.org/wiki/Manual:JavaScript_unit_testing
[2] https://phabricator.wikimedia.org/phame/post/view/96/fast_and_isolated_js_u…
Hi,
tl;dr: The "fonts" submodule in operations/mediawiki-config will go away
For a very long time, we've had a Git repository,
operations/mediawiki-config/fonts, that contains a random assortment of
font files copied out of an Ubuntu appserver back in 2008. My
understanding is that these fonts were only ever used by the
EasyTimeline extension via ploticus.
The current README ends with:
> We can presumably dump it if we kill ploticus running from app servers.
> -- brion 2008-12-09
...which has now happened with the migration to Shellbox. During the
build process, the fonts are copied out of the Git repository into the
Shellbox container[1].
I intend to:
1) remove the fonts submodule from the operations/mediawiki-config
repository, removing it from all appservers[2].
2) Empty out most of the fonts repository so it only contains the 3
fonts we actually use for Timelines (FreeSans, FreeSansWMF, unifont)[3].
I am mostly sending this email in case someone else is using this
repository for fonts or expecting this path to exist on appservers, in
which case, please say something.
Semi-relatedly, there is an open task to remove all the fonts installed
via Debian packages from appservers, now that all thumbnailing and image
generation happens on thumbor/shellbox servers[4].
[1]
https://gerrit.wikimedia.org/g/mediawiki/libs/Shellbox/+/e6c19d0927b65e3c50…
[2] https://gerrit.wikimedia.org/r/723652
[3] https://gerrit.wikimedia.org/r/732792
[4] https://phabricator.wikimedia.org/T294378
-- Kunal
Hello! I am Ayush Gadre. Sophomore at Institute of Engineering and
Technology DAVV Indore. I want to learn about open source and want to
contribute in your organization.
1. Education : - B.Tech
2. Experience :- Web development Internship from LetsGrowMore
3. Skills :- HTML, CSS, JS and React JS
I would love to join your open source community and learn from your
mentors. I'm looking forward to being accepted to your group to learn more
about the projects. So, I hereby request you to please add me in
your mailing list or on your channel.
Github :- https://github.com/Ayushgadre
Linkedin :- https://www.linkedin.com/in/ayushgadre/
Thank you for your consideration.
Regards,
Ayush Gadre
This email is a summary of the Wikimedia production deployment of
1.38.0-wmf.5 which has been successfully completed last week.
* Conductor: Antoine "hashar" Musso
* Backup Conductor: Ahmon Dancy
* Blocker Task: T281169 <https://phabricator.wikimedia.org/T281169>
* Current Status <https://versions.toolforge.org>
🔢 Numbers
Sparklines comparing with the last 5 trains.
* 351 Patches ██▁▂█
* 0 Rollbacks ▁▃█▁▁
* 0 Days of delay ▁▁█▁▁
* 3 Blockers ▄█▇█▁
✨ Traintastic Folks 😻
Thanks to folks who reported or resolved blockers:
* Jon Robson, remembered me about JavaScript client side errors to be
taken of
* Elena and Joseph Seddon, flagged a blocker for group 1 ahead of time
and got it fixed with Simone Cuomo.
* Subramanya Sastry, who has noiticed a missed class in Parsoid
* C. Scott, Lucas Werkmeister who promptly addressed deprecation errors
* Ahmon Dancy for being the backup conductor and closely watching
error logs
Antoine "hashar" Musso