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

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

    XMLWordPrintable

Details

    • Out of scope
    • Jumbo: > 45 days
    • Prokopovych
    • 100

    Description

      This UXPROD was created so that the Prokopovych 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-INVENTORY 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.

      TestRail: Results

        Attachments

          Issue Links

            is cloned by

            New Feature - New feature requests UXPROD-3388 Tech Debt: Create MOD-INVENTORY tests with Karate - NOT SCHEDULED

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed
            is defined by

            Tech Debt - MODINV-509 Create Karate test for Inventory: When creating a new instance by using the edit form, and all edits are saved and the form is closed, then a new instance is created , and will be displayed in detailed view (inv-1)

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

            Tech Debt - MODINV-510 Create Karate test for Inventory: When creating a new holdings by using the edit form, and all edits are saved and the form is closed, then a new holdings is created , and will be displayed associated with the given instance (inv-2)

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

            Tech Debt - MODINV-511 Create Karate test for Inventory: When creating a new item by using the edit form, and all edits are saved and the form is closed, then a new item is created , and will be displayed associated with it's given holdings and instance (inv-3)

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

            Tech Debt - MODINV-512 Create Karate test for Inventory: When duplicating an existing instance, then a new instance is created with a unique UUID and Instance HRID (inv-4)

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

            Tech Debt - MODINV-513 Create Karate test for Inventory: When duplicating an existing holdings, then a new Holdings is created with a unique UUID and Holdings HRID (inv-5)

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

            Tech Debt - MODINV-514 Create Karate test for Inventory: When duplicating an existing Item, then a new Item is created with a unique UUID and Item HRID (inv-6)

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

            Tech Debt - MODINV-515 Create Karate test for Inventory: When deleting a holdings, the deletion can not be performed if any item is associated with it, or eventually dependencies with other apps. (inv-7)

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

            Tech Debt - MODINV-516 Create Karate test for Inventory: When deleting an item, the deletion can not be performed if eventually dependencies with other apps. (inv-8)

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

            Tech Debt - MODINV-517 Create Karate test for Inventory: When connecting a journal with it's preceeding title, available in the libraries collection, then this preceeding title will connect the given journal as it's succeeding title (inv-9)

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

            Tech Debt - MODINV-518 Create Karate test for Inventory: When connecting a journal with it's succeeding title, available in the libraries collection, then this succeeding title will connect the given journal as it's preceeding title (inv-10)

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

            Tech Debt - MODINV-519 Create Karate test for Inventory: When connecting a given instance with it's child instance (Instance relationship), available in the libraries collection, then this child instance will connect the given instance as it's parent instance (inv-11)

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

            Tech Debt - MODINV-520 Create Karate test for Inventory: When connecting a given instance with it's parent instance (Instance relationship), available in the libraries collection, then this parent instance will connect the given instance as it's child instance (inv-12)

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

            Tech Debt - MODINV-521 Create Karate test for Inventory: When editing the holdings, the permanent holdings location will be listed in a drop down menu. The drop down menu is generated from the library specifik locations defined in Settings > Tenant > Location setup (inv-13)

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

            Tech Debt - MODINV-522 Create Karate test for Inventory: When editing the holdings, the temporary holdings location will be listed in a drop down menu. The drop down menu is generated from the library specifik locations defined in Settings > Tenant > Location setup (inv-14)

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

            Tech Debt - MODINV-523 Create Karate test for Inventory: When editing the item, the permanent item location will be listed in a drop down menu. The drop down menu is generated from the library specifik locations defined in Settings > Tenant > Location setup (inv-15)

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

            Tech Debt - MODINV-524 Create Karate test for Inventory: When editing the item, the temporary item location will be listed in a drop down menu. The drop down menu is generated from the library specifik locations defined in Settings > Tenant > Location setup (inv-16)

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

            Tech Debt - MODINV-525 Create Karate test for Inventory: The holdings effective location is the value computed by FOLIO as the first value it finds going down list order provided (inv-17)

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

            Tech Debt - MODINV-526 Create Karate test for Inventory: The item effective item location is the value computed by FOLIO as the first value it finds going down list order provided (inv-18)

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

            Tech Debt - MODINV-527 Create Karate test for Inventory: When assigning a barcode to an item, the item record can only be saved if the barcode is unique (inv-19)

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

            Tech Debt - MODINV-537 Create Karate test for Inventory: When an instance record has instance source MARC, then the source record can be viewed in SRS (if SRS is installed) (inv-29)

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

            Tech Debt - MODINV-538 Create Karate test for Inventory: When an instance record has instance source FOLIO, and no underlying MARC record is associated, then there is no View source option in the Action menu (inv-30)

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

            Tech Debt - MODINV-539 Create Karate test for Inventory: When move of an item to a different holdings within the same instance by using drag and drop, then the item will be associated with the desgnated holdings (inv-31)

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

            Tech Debt - MODINV-540 Create Karate test for Inventory: When move of a holdings and possible items to a different instance by using drag and drop, then the iholdings with the relevant items be associated with the desgnated instance (inv-32)

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

            Tech Debt - FAT-143 mod-inventory: Setup API Karate tests in the module

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

            Tech Debt - FAT-163 mod-inventory: Create test plan to cover functionality with API Karate test

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

            Tech Debt - FAT-172 mod-inventory: Implement API Karate tests based on Test plans

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

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

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

            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-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

                singhAdesh Adesh Singh
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases