Uploaded image for project: 'ui-users'
  1. ui-users
  2. UIU-675

Enforce Manual Patron Blocks

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      UNAM

      Description

      UICHKOUT-33 also updates Borrower information so please make that change at the same time.

      Purpose: Enforcement of manual patron block "block actions" specified by staff member who created the block. This may include one or more of the following: Borrowing, Renewals, Requests

      BORROWING SCENARIOS

      1. Scenario
        Given the Check out page
        When Borrower has a block in place
        Then Patron blocked from borrowing pop-up (as shown in attached mock-up Blocked-checkout.png) should appear immediately upon scanning patron's barcode, along with Patron blocks count at end of usual Borrower information (as shown in attached mock-up Blocked-checkout.png)--both the count "1" and the text "block in place" should be links to the User Information page with Patron blocks section open
      2. Scenario
        Given the Patron blocks count ("1" in the mock-up) on the Check out page (as shown in attached mock-up Blocked-checkout.png)
        When clicked
        Then open User Information page with Patron blocks section open (as shown in attached mock-up 1-user-details-patron-blocks.png)
      3. Scenario
        Given the Patron blocks "block in place" text on the Check out page (as shown in attached mock-up Blocked-checkout.png)
        When clicked
        Then open User Information page with Patron blocks section open (as shown in attached mock-up 1-user-details-patron-blocks.png)
      4. Scenario
        Given the Block details button on the Patron blocked from borrowing pop-up (as shown in attached mock-up Blocked-checkout.png)
        When clicked
        Then open User Information page with Patron blocks section open (as shown in attached mock-up 1-user-details-patron-blocks.png)
      5. Scenario
        Given the X or Close button on the Patron blocked from borrowing pop-up (as shown in attached mock-up Blocked-checkout.png)
        When pressed
        Then close the Patron blocked from borrowing pop-up and remain at Check out page with Borrower information displaying
      6. Scenario
        Given the closed Patron blocked from borrowing pop-up and Patron block count > 0 (as shown in attached mock-up Blocked-checkout.png)
        When item scanned
        Then Patron blocked from borrowing pop-up (as shown in attached mock-up Blocked-checkout.png) should appear again

      RENEWING SCENARIOS

      1. Scenario
        Given the Open loans page, with multiple loans selected and Renew button pressed (as shown in attached mock-up Blocked-renew-multiple.png)
        When borrower has a block in place
        Then Patron blocked from renewing pop-up (as shown in attached mock-up Blocked-renew-multiple.png) should appear immediately after button is pressed
      2. Scenario
        Given the Open loans page, with ellipsis action Renew selected for one loan (as shown in attached mock-up Blocked-renew-single.png)
        When borrower has a block in place
        Then Patron blocked from renewing pop-up (as shown in attached mock-up Blocked-renew-single.png) should appear immediately after action is selected
      3. Scenario
        Given the Block details button on the Patron blocked from renewing pop-up (as shown in attached mock-ups Blocked-renew-multiple.png and Blocked-renew-single.png)
        When clicked
        Then open User Information page with Patron blocks section open (as shown in attached mock-up 1-user-details-patron-blocks.png)
      4. Scenario
        Given the X or Close button on the Patron blocked from renewing pop-up (as shown in attached mock-ups Blocked-renew-multiple.png and Blocked-renew-single.png)
        When pressed
        Then close the Patron blocked from renewing pop-up and remain at Open loans page

      REQUESTING SCENARIOS

      1. Scenario
        Given the New request page
        When borrower has a block in place
        Then Patron blocked from requesting pop-up (as shown in attached mock-up Blocked-requests.png) should appear immediately after Requester look-up takes place; clear out Item information
      2. Scenario
        Given the Block details button on the Patron blocked from requesting pop-up (as shown in attached mock-up Blocked-requests.png)
        When clicked
        Then open User Information page with Patron blocks section open (as shown in attached mock-up 1-user-details-patron-blocks.png)
      3. Scenario
        Given the X or Close button on the Patron blocked from requesting pop-up (as shown in attached mock-up Blocked-requests.png)
        When pressed
        Then close the Patron blocked from requesting pop-up and remain at New request page
      4. Scenario
        Given the closed Patron blocked from requesting pop-up and Patron block count > 0
        When Item information entered
        Then Patron blocked from requesting pop-up (as shown in attached mock-up Blocked-requests.png) should appear again

        TestRail: Results

          Attachments

          1. 1-user-details-patron-blocks.png
            1-user-details-patron-blocks.png
            150 kB
          2. Blocked-checkout.png
            Blocked-checkout.png
            87 kB
          3. Blocked-renew-multiple.png
            Blocked-renew-multiple.png
            104 kB
          4. Blocked-renew-single.png
            Blocked-renew-single.png
            102 kB
          5. Blocked-requests.png
            Blocked-requests.png
            118 kB

            Issue Links

              Activity

                People

                Assignee:
                Luis Luis Contreras
                Reporter:
                hollyolepm Holly Mistlebauer
                Tester Assignee:
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases