There are a lot of moving parts with homepage code, VE, dialogs, etc, having some coverage of this via browser tests would be nice.
TBD is which specific components we want to try to target
There are a lot of moving parts with homepage code, VE, dialogs, etc, having some coverage of this via browser tests would be nice.
TBD is which specific components we want to try to target
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T284512 [EPIC] Empower others to develop new, and extend existing, editing experiences | |||
Open | None | T299620 Implement automated testing for core editing functionality | |||
Open | None | T296187 Selenium Tests for VisualEditor | |||
Open | KStoller-WMF | T276517 [EPIC] Growth: "add a link" structured task 3.0 | |||
Resolved | kostajh | T276860 Review test coverage for add link feature | |||
Resolved | kostajh | T284611 Selenium tests for add link feature |
Change 698872 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):
[mediawiki/extensions/GrowthExperiments@master] selenium: Add basic workflow test for add link feature
Change 699705 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):
[mediawiki/extensions/GrowthExperiments@master] selenium: Test for AddLink
Change 698872 merged by jenkins-bot:
[mediawiki/extensions/GrowthExperiments@master] selenium: AddLink configured Special:Homepage
Stalled on T285649: Switch all Quibble Selenium and api-testing jobs to use apache. We need apache in order for VisualEditor + Parsoid to work in CI.
Maybe I'm not understanding this correctly, but looks like VisualEditor (and Parsoid?) work in CI, see 345146.
Yeah, now I am confused. Because my test would definitely just hang in CI, but it was also not possible (maybe you know a way?) to capture the browser console logs to see what the specific error was.
Also, for your test, I think it's possible that edit interactions specifically won't work -- I'm curious to see what happens when the Selenium test presses the Publish button.
Change 721024 had a related patch set uploaded (by Zfilipin; author: Zfilipin):
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
It might be possible with addConsoleLogs. You'll have to use spec reported instead of the default dot reporter, but that should be a simple configuration change. I would make a commit testing it, but I don't know what you would like to capture. Let me know if you need help. Feel free to set up a video meeting (my calendar is usually up to date) if you would like to pair on this.
Nothing exploded, but it either didn't save or it takes a very long time to save. I'll further increase timeout, but I don't have much hope it will help.
Change 721024 abandoned by Zfilipin:
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
Reason:
just a test
Change 721024 restored by Kosta Harlan:
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
Change 721024 abandoned by Kosta Harlan:
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
Reason:
Change 721024 restored by Zfilipin:
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
Change 721024 abandoned by Zfilipin:
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
Reason:
Change 721024 restored by Zfilipin:
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
Change 721024 abandoned by Zfilipin:
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
Reason:
Change 742939 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):
[integration/config@master] zuul: Add VisualEditor/parsoid dependencies to GrowthExperiments
Change 721024 restored by Kosta Harlan:
[mediawiki/extensions/VisualEditor@master] WIP VisualEditor should save an edit
This test passes now that T285649: Switch all Quibble Selenium and api-testing jobs to use apache is done.
Change 699705 merged by jenkins-bot:
[mediawiki/extensions/GrowthExperiments@master] selenium: Test for AddLink
Change 752616 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):
[mediawiki/extensions/GrowthExperiments@master] selenium: Remove Parsoid loading code
Change 742939 merged by jenkins-bot:
[integration/config@master] zuul: Add VisualEditor/parsoid dependencies to GrowthExperiments
Change 752616 merged by jenkins-bot:
[mediawiki/extensions/GrowthExperiments@master] selenium: Conditionally load Parsoid
No, it's something specific to a GrowthExperiments plugin that uses VE.
@Etonkovidova not sure there is anything to QA here; we have selenium tests for add link now.