Page MenuHomePhabricator

Recreate browser tests for detecting edit conflicts after form resubmission
Closed, ResolvedPublic5 Estimated Story Points

Description

We used to have browser tests that assert that an edit conflict is detected if the same form is submitted twice. However, for some reasons they did not work in CI, and so they were skipped a long time ago. Quick attempts to fix the underlying problem were not successful (see Reenable browser test to check for edit conflicts (I4df0ff86)).

So, those tests were effectively dead code for a long time and thus deleted: selenium: Delete tests disabled for more than 1 year (I9507e539)

However, we may still wish to verify that behavior.

Acceptance criteria:

  • there exists a test that asserts that the edit schema form detects an edit conflict when re-submitting the same form
  • there exists a test that asserts that the SetEntitySchemaLabelDescriptionAliasesPage detects an edit conflict when re-submitting the same form

Event Timeline

Change 859503 had a related patch set uploaded (by Michael Große; author: Zfilipin):

[mediawiki/extensions/EntitySchema@master] selenium: Delete tests disabled for more than 1 year

https://gerrit.wikimedia.org/r/859503

Change 813642 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/EntitySchema@master] Reenable browser test to check for edit conflicts

https://gerrit.wikimedia.org/r/813642

Change 813642 abandoned by Michael Große:

[mediawiki/extensions/EntitySchema@master] Reenable browser test to check for edit conflicts

Reason:

This did not work out. But what was tried here might be useful in the future. Further work will be tracked in T323763

https://gerrit.wikimedia.org/r/813642

Change 859503 merged by jenkins-bot:

[mediawiki/extensions/EntitySchema@master] selenium: Delete tests disabled for more than 1 year

https://gerrit.wikimedia.org/r/859503

Prio Notes:

  • Does not affect end users / production
  • Affects development efforts (maintenance aspects)
  • Does not affect onboarding efforts
  • Does not affect external / additional stakeholders
karapayneWMDE set the point value for this task to 5.Dec 20 2022, 2:31 PM

If the problem was that Chromium didn’t preserve the baserevid input when submitting the edit form and then going back before submitting it a second time – maybe we can open two windows with the edit page instead, and submit those?

Change 875961 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/EntitySchema@master] Recreate browser tests for detecting edit conflicts

https://gerrit.wikimedia.org/r/875961

Change 875961 merged by jenkins-bot:

[mediawiki/extensions/EntitySchema@master] Recreate browser tests for detecting edit conflicts

https://gerrit.wikimedia.org/r/875961

ItamarWMDE updated the task description. (Show Details)

Looks great, nice trick with the double window, and thanks for deleting old disabled tests