Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-3347

Tech Debt: Create MOD-CIRCULATION tests with Karate - R1 2022

    XMLWordPrintable

Details

    • Lotus R1 2022
    • Out of scope
    • Low
    • Jumbo: > 45 days
    • Vega
    • 100

    Description

      This UXPROD was created so that the Prokopovych (now Vega) Team has time set aside to develop the Karate tests needed for our APIs.

      It is unlikely that all of this work will all be completed for the Lotus (R1 2022) release.  Anything that is not completed will be split from this feature and linked to a yet-to-be-created feature that will be named "Tech Debt: Create MOD-CIRCULATION tests with Karate - R2 2022".

      Feel free to create additional task/sub-tasks as needed.  Just make sure they are linked to this feature as "is defined by". 

      First priority is mod-circulation, then mod-inventory and then mod-users.

      https://docs.google.com/spreadsheets/d/1xe2F6BWHvLscHrSekTl6JtDIU4FQa0t6JH1mc8gc99s/edit#gid=1746951879&range=1:1004

      TestRail: Results

        Attachments

          Issue Links

            is cloned by

            New Feature - New feature requests UXPROD-3462 Tech Debt: Create MOD-CIRCULATION tests with Karate - R2 2022

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is defined by

            Tech Debt - FAT-993 Create Karate test for Loans: When patron and item id's entered at checkout, post a new loan using the circulation rule matched (circ-3)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-996 Create Karate test for Loans: When an existing loan is checked in, post a new checkin record (circ-6)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-997 Create Karate test for Loans: When an existing loan is recalled, update dueDate according to loan policy, update dueDateChangedByRecall (circ-7)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-998 Create Karate test for Loans: When an existing loan is declared lost, update declaredLostDate,item status to declared lost and bill lost item fees per the Lost Item Fee Policy (circ-8)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-999 Create Karate test for Loans: When an existing loan is claimed returned, update claimedReturnedDate, suspend any lost item fees billed and refund any lost item fees paid (circ-9)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1002 Create Karate test for Loans: When get loans for a patron is called, return a paged collection of loans for that patron with all data as specified in the circulation/loans API (circ-12)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1003 Create Karate test for Loans: When an loaned item is checked in at a service point that serves its location and no request exists, change the item status to Available (circ-13)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1004 Create Karate test for Loans: When a loaned item is checked in at a service point that does not serve its location and no request exists, change the item status to In-transit and destination to primary service point for its location (circ-14)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1005 Create Karate test for Loans: When a loaned item is checked in at a service point that does not serve its location and a request exists, change the item status to In-transit and destination to pickup loaction in the request (circ-15)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1006 Create Karate test for Loans: When an requested loaned item is checked in at a service point designated as the pickup location of the request, change the item status to awaiting-pickup (circ-16)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1007 Create Karate test for Loans: When an item has the status intellectual item, do not allow checkout (circ-17)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1008 Create Karate test for Loans: When an item has the status of restricted, allow checkout with override (circ-18)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1009 Create Karate test for Loans: When an item that had the status of restricted that was checked out is checked in, set the item status to Available (circ-19)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1010 Create Karate test for Loans: When an item has the status of in process allow checkout (circ-20)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1011 Create Karate test for Loans: When an item that had the status of in process that was checked out is checked in, set the item status to Available (circ-21)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1012 Create Karate test for Loans: When an item has the status of on order allow checkout (circ-22)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1013 Create Karate test for Loans: When an item that had the status of on order that was checked out is checked in, set the item status to Available (circ-23)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1017 Create Karate test for Loans: When an overdue item is returned, an overdue fine is billed per the Overdue Fine Policy (circ-27)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1030 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a page request when the applicable request policy disallows pages (should fail) (circ-41)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1031 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a hold request when the applicable request policy disallows holds (should fail) (circ-42)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1032 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a recall request when the applicable request policy disallows recalls (should fail) (circ-43)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1033 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a page request when the applicable request policy allows pages, but items is not of status Available or Recently returned (should fail) (circ-44)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1034 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a hold request when the applicable request policy allows holds, but item is of status Available, Recently returned, In process (not requestable), Dec...

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1035 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a recall request when the applicable request policy allows recalls, but item is of status Available, Recently returned, Missing, In process (not requ...

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1036 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a page request when the applicable request policy allows pages and item status is Available or Recently returned (circ-47)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1037 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a hold request when the applicable request policy allows holds and item status is not Available, Recently returned, In process (not requestable), Dec...

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1038 Create Karate test for Requests: Given an item Id, a user Id, and a pickup location, attempt to create a recall request when the applicable request policy allows recalls and item status is not Available, Recently returned, Missing, In process (not requ...

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. FAT-1096 Vega - Introduce Team Name into Karate API tests

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Tech Debt - FAT-1142 Fix policies' influences on mod-circulation module

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1165 Fix Karate test for mod-patron-blocks (automatedPatronBlocks.feature) with purpose to use relevant page request

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            New Feature - New feature requests UXPROD-3138 Tech Debt: Create MOD-USERS tests with Karate - R1 2022

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-3348 Tech Debt: Create MOD-INVENTORY tests with Karate - R1 2022

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-3393 Tech Debt: Create EDGE-PATRON tests with Karate - R1 2022

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-3394 Tech Debt: Create EDGE-RTAC tests with Karate - R1 2022

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                hollyolepm Holly Mistlebauer
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases