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

NFR: Create integration tests for key Data Import functionality using Karate (Kiwi)

    XMLWordPrintable

Details

    • Medium < 5 days
    • Very Small (VS) < 1day
    • Low
    • Jumbo: > 45 days
    • Folijet
    • 114

    Description

      Feature to create integration tests for main workflows in data import. Allows for testing integration between modules on live environment; test all endpoints; move API tests from modules to these integration tests. Can't really do end to end from uploading file to checking results after import; not supported by Karate

      Preliminary estimate 45 days for completing this feature based on team estimation.
      Will be continued in Lotus by UXPROD-3121

      Kateryna Senchenko to review the remaining stories and update if necessary; some will need to be rewritten as workflows; some will move to the Lotus feature

      Preparation: Team will allocate time for the following

      • Setup Karate in modules (also link these issues to FAT-2) - DONE
      • Define test plans (also link these issues to FAT-152)
      • Implement Karate tests (also link these issues to FAT-892)

      https://wiki.folio.org/display/FOLIJET/API+Integration+Testing

      Scope for Kiwi

      • Team forecast for Karate test coverage up to end of September.
        • Create all inventory types - end of Sept
        • Update for all inventory types - including matches, MARC modify and updates, field protections: end of Sept:
        • Stretch: Match on instance + instance update.
        • Added scenario for creating EDIFACT invoices
        • Added scenario for file extensions, plus beginning of covering creation of profiles for Data Import

      Within the tests:

      • Will need to configure the environment
      • Will need appropriate MARC/EDIFACT files (1 record in the file)
      • Will need the appropriate profiles
      • Test covers the workflow from profile creation through finishing the UI log
      • Reset environment after tests
      • Also need some ramp-up time to learn Karate

      Acceptance criteria:

      TestRail: Results

        Attachments

          Issue Links

            defines

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-47 Batch Importer (Bib/Acq)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Analysis Complete
            is continued by

            New Feature - New feature requests UXPROD-3121 NFR: Create integration tests for key Data Import functionality using Karate (Lotus)

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

            Task - A task that needs to be done. FAT-27 SPIKE: Investigate if API Karate tests integrated with TestRail are applicable for data-import related flows

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

            Tech Debt - FAT-139 Cover mod-data-import with API tests

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

            Tech Debt - FAT-178 mod-source-record-storage: 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-179 mod-source-record-manager: 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-180 mod-data-import: 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-181 mod-data-import-converter-storage: 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-183 mod-data-import: 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

            Task - A task that needs to be done. FAT-914 Spike: Prepare for API Karate tests

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

            Task - A task that needs to be done. FAT-936 mod-data-import-converter-storage: Create profile for CREATE Instance, Holdings, Items

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

            Task - A task that needs to be done. FAT-937 mod-data-import: Implement 'Create Instances, Holdings, and Items' scenario - INTEGRATION

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

            Task - A task that needs to be done. FAT-939 mod-data-import: Implement 'Modify MARC_Bib, update Instances, Holdings, and Items' 1 scenario - - INTEGRATION

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

            Task - A task that needs to be done. FAT-947 mod-data-import: Set up default data for data-import integration tests

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

            Tech Debt - FAT-956 Cover file-extensions.feature with API tests

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

            Tech Debt - FAT-968 Create API test for EDI invoice import workflow - INTEGRATION

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

            Task - A task that needs to be done. MODDATAIMP-299 Test Update action for Instances

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

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. FAT-2 Karate Setup in the Modules - Tech Debt

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

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. FAT-152 API Karate tests plan creation and estimate - Tech Debt

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

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. FAT-892 API Karate tests implementation - Tech Debt

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

            Tech Debt - FAT-915 Spike: Decide on an approach for creating end-to-end automated tests

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

            Page Loading...

            Activity

              People

                abreaux Ann-Marie Breaux
                abreaux Ann-Marie Breaux
                Oleksii Kuzminov Oleksii Kuzminov
                Ann-Marie Breaux Ann-Marie Breaux
                Oleksii Kuzminov Oleksii Kuzminov
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases