Create tests that describe the desired functionality
Open, NormalPublic5 Story Points



The following behavior is validated with browser tests

Testable without Cirrus search and any actual search interaction:

  • info i's are visible on the page and their popups are not empty
  • searching for combinations of words: Each of the offered fields should be used and verified at least once
    • right URL / page with correct GET request should be fine
  • searching for a file
    • file namespace is added
    • depending on the file type dimension fields are shown
  • namespace search behavior
    • when clicking on all, all namespaces are selected
    • selected namespaces are unselectable in the dropdown list
    • Unselecting a single namespace after all had been clicked, unselects all
    • adding a namespace to complete the list of all namespaces, all is automatically selected

No search results needed:

  • search preview of the search form after form submit: The advanced search form should still contain all values after a form submit, but now it should be collapsed
    • and the opposite: expanding the search form hides the preview pills
Restricted Application added a project: TCB-Team. · View Herald TranscriptJun 7 2017, 4:34 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Pablo-WMDE updated the task description. (Show Details)Jul 26 2017, 11:17 AM
Pablo-WMDE set the point value for this task to 8.
Lea_WMDE triaged this task as Normal priority.Jan 10 2018, 2:45 PM
Lea_WMDE updated the task description. (Show Details)
Lea_WMDE changed the point value for this task from 8 to 5.

Change 405905 had a related patch set uploaded (by Zoranzoki21; owner: Tonina Zhelyazkova):
[mediawiki/extensions/AdvancedSearch@master] Add first tests to search page

Tonina_Zhelyazkova_WMDE updated the task description. (Show Details)EditedJan 24 2018, 2:01 PM

The AC has been edited to make the test hierarchy more clear.
"Search for file" should be in its own category rather than under "Searching for combinations of words"

Change 405905 had a related patch set uploaded (by Zoranzoki21; owner: Tonina Zhelyazkova):
[mediawiki/extensions/AdvancedSearch@master] Add first tests to search page

Change 405905 had a related patch set uploaded (by Tonina Zhelyazkova; owner: Tonina Zhelyazkova):
[mediawiki/extensions/AdvancedSearch@master] Add first tests to search page

@Lea_WMDE: We discovered that for our test code we need to override methods that are affected by an upcoming change in OOJS UI (, related to this issue T181691: [Pre-wmf.11] Special:Preferences asks for leave confirmation even when no changes were made. The OOJS change is already merged, but the latest mediawiki core does not use the change yet. Should we

a) postpone this ticket until the newest OOJS version is in mediawiki core,
b) split off all the tests related to dropdown widgets (file type, file height, file width) and postpone those,
c) create puke-worthy workaround code in our AdvancedSearch components and file a ticket to remember to clean it up.

Change 405905 merged by jenkins-bot:
[mediawiki/extensions/AdvancedSearch@master] Add first tests to search page

Deployed on the test wiki. The test server still has the old OOUI version. That means the new method FileTypeSelection.setOptionsData won't be called and the menu items in the file type selections won't get unique class names. This does not affect functionality and as long as we don't run browser tests against the test wiki it also won't affect the browser tests.

After looking at and the DropdownInputWidget code I saw that FileTypeSelection.setOptionsData overrides a private method, which means it could break at any time. I've opened issue T186901: Add ability to override menu item creation for DropdownInputWidget and proposed a change to OOUI so we can override menu item creation better in the future.