Uploaded image for project: 'Folio Automation Testing'
  1. Folio Automation Testing
  2. FAT-914

Spike: Prepare for API Karate tests

    XMLWordPrintable

Details

    • Folijet Sprint 120
    • 5
    • Folijet

    Description

      Purpose/Overview:
      Review requirements for Karate
      Create test plan to cover functionality with API Karate test
      Set up environment so that Karate test-writing and implementation can proceed

      Approach:

      https://wiki.folio.org/display/FOLIJET/Karate+test+plan+for+cucumber+report

      Acceptance criteria:
      Undefined scenarios added and shown in Cucumber report

      TestRail: Results

        Attachments

          Issue Links

            defines

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

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

            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
            has to be done before

            Tech Debt - FAT-138 mod-source-record-storage: Implement API Karate tests based on Test plans

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

            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-940 mod-data-import: Implement 'Match MARC-to-MARC and update Instances, Holdings, and Items' 2 scenario - INTEGRATION

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

            Task - A task that needs to be done. FAT-941 mod-data-import: Implement 'Match MARC-to-MARC and update Instances, Holdings, and Items' 3 scenario - INTEGRATION

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

            Task - A task that needs to be done. FAT-942 mod-data-import: Implement 'Match MARC-to-MARC and update Instances, Holdings, and Items' 4 scenario - INTEGRATION

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

            Task - A task that needs to be done. FAT-943 mod-data-import: Implement 'Match MARC-to-MARC and update Instances, Holdings, and Items' 5 scenario - INTEGRATION

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

            Task - A task that needs to be done. FAT-944 mod-data-import: Implement 'Match MARC-to-MARC and update Instances, fail to update Holdings, and Items' scenario - INTEGRATION

            • 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-945 mod-data-import: Implement 'Match MARC-to-MARC and update Instances, Holdings, fail to update Items' scenario - INTEGRATION

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

            Page Loading...

            Activity

              People

                Kateryna Senchenko Kateryna Senchenko
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases