Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-157

Data import settings page's 3rd pane for File Extensions: Search box



    • EPAM BatchLoader Sprint 12
    • 8
    • Folijet


      Purpose: To be able to search existing settings for handling various types of file extensions. The search box will allow a user to filter the list of file extensions based on the entered string.

      As a staff person
      I want to be able to filter settings related to file extensions for the Data Import app
      So that I can narrow down the results to work with them better

      Live prototype:

      Brief video walk-through
      https://www.dropbox.com/s/3slcv4v49qm92rv/2018-11-06-data-import-19.mp4?dl=0 (see 4:10-5:10 in the video)


      1. Scenario 1
        • Given the Data Import Settings File extensions
        • When a User wants to search/filter the existing file extension
        • Then they should be able to enter data in the search box at the top of the 3rd pane (list of all existing file extensions) See attachment File extension search box.PNG
      2. Scenario 2
        • Given a string entered into the search box
        • When a User presses Enter on their keyboard , or the Enter button to the right of the Search box
        • Then FOLIO should check for that string against the following fields in the file extension record:
          • Extension
          • Data type(s) [one at a time, not combined]
      3. Scenario 3
        • Given a string entered into the search box
        • When a User views the list of existing file extensions
        • Then the entered text should be highlighted in the list
        • And the list should be filtered down to only display file extensions that include that string. See attachment 26-Settings Job profiles filtered.png as an example
      4. Scenario 4
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot [no screenshot, but A-M confirmed recent coverage % in SonarCloud)

      NOTES (See UIDATIMP-163)

      • Consider changing the search (filter) to trigger without an explicit enter in the future. Some issues with that function in Inventory previously, so we're using the explicit Enter key or Enter button for now.
      • Add a reset "x" in the search box to allow for the search data to be deleted without back-spacing. Since back-spacing works, this is a "nice to have" instead of a "must have"

      TestRail: Results


          Issue Links



                abreaux Ann-Marie Breaux
                abreaux Ann-Marie Breaux
                0 Vote for this issue
                2 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases