Uploaded image for project: 'ui-inventory'
  1. ui-inventory
  2. UIIN-1065

Cate's Copy - Search. Item segment. Search option for Effective call numbers (item), normalized - 1st phase

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      Prokopovych

      Description

      Scenarios:
      Assume the following item records exist

      Example Effective call number prefix Effective call number Effective call number suffix
      1 ? ? ?
      2 ? ? ?
      3 ? ? ?
      1. Scenario
        • Login to FOLIO Snapshot, go to Inventory, Search & filter pane, and select the Item segment
        • When the search options menu is opened
        • Then a new "Effective call number (item), normalized" option should display:
      2. Scenario
        • Given the Effective call number (item), normalized
        • When a search term is entered
        • Then search is left anchored meaning instances containing the following items are expected: (CB: We need to update this table with examples specific to this requirement)
          Search Expected result
          8 GB439 6 Example 1
          JUR R III 54 (1) Schm 1850 Example 2
          94 NF 14 1 3792-3835 No results
      3. Scenario
        • Given the Effective call number (item), normalized
        • When a search term is entered
        • Then right truncation is set as a default instances containing the following items are expected: (CB: We need to update this table with examples specific to this requirement)
          Search Expected result
          8 GB439 6 Example 1
          JUR R III 54 (1) Schm 1850 Example 2
          94 NF 14 1 3792-3835 No results
      4. Scenario
        • When search on the Effective call number (item), normalized
        • Then normalization between lower casing and capitalized letters are happening
      5. Scenario
        • When search on any the Effective call number (item), normalized
        • Then normalization by stripping whitespace are happening
      6. Scenario
        • When search on the "Effective call number (item), normalized" search option
        • Then normalization by stripping hypen is happening
      7. Scenario
        • When search on the "Effective call number (item), normalized" search option
        • Then normalization by stripping period is happening
      8. Scenario
        • When search on the "Effective call number (item), normalized" search option
        • Then normalization by stripping comma is happening
      9. Scenario
        • When search on the "Effective call number (item), normalized" search option
        • Then normalization by stripping colon is happening
      10. Scenario
        • When search on the "Effective call number (item), normalized" search option
        • Then normalization by stripping slash is happening
      11. Scenario
        • When search on the "Effective call number (item), normalized" search option
        • Then normalization by stripping bracket is happening
      12. Scenario
        • When search on the "Effective call number (item), normalized" search option
        • Then normalization by stripping parenthesis is happening
      13. Scenario
        • When a user wants to search on Call number, normalized then following search options are possible in normalized form:
          Search Expected result
          8 GB439 6 8 G.B.439 :6
          JUR R III 54 (1) Schm 1850 JUR:R III:54:(1):Schm:1850
          94 NF 14 1 3792-3835 94 NF 14/1:3792-3835
          Z 557 54 1961 62 7-12 Z 557: 54.1961/62,7-12
          Y 43839 2017/18 Y 43839 (2017/18)
      14. Scenario
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                charlotte Charlotte Whitt
                Tester Assignee:
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases