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

mod-kb-ebsco-java: Implement API Karate tests - Packages

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      eHoldings Sprint 124
    • Story Points:
      3
    • Development Team:
      Spitfire
    • Epic Link:

      Description

      Purpose/Overview:
      Karate implementation based on test plans is created

      Acceptance criteria:

      1. API Tests are created at  https://github.com/folio-org/folio-integration-tests
      2. Test are shown as passed in Cucumber report.

        TestRail: Results

          Attachments

            Issue Links

            has to be done after

            Tech Debt - FAT-192 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - KB credentials

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

            Tech Debt - FAT-905 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Providers

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

            Tech Debt - FAT-906 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Packages

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

            Tech Debt - FAT-907 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Titles

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

            Tech Debt - FAT-908 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Resources

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

            Tech Debt - FAT-909 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Status/Proxy/Tags

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

            Tech Debt - FAT-910 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Access types

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

            Tech Debt - FAT-911 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - User Assignment

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

            Tech Debt - FAT-912 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Usage Consolidation

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

            Tech Debt - FAT-976 mod-kb-ebsco-java: Implement API Karate tests - Titles

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

            New Feature - New feature requests UXPROD-3320 Spitfire: Karate API Integration Testing (NFR) - Lotus work

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

              Activity

                People

                Assignee:
                Shans Shans Kaluhin
                Reporter:
                Oleksii Petrenko Oleksii Petrenko
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases