Details
-
Tech Debt
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Duplicate
-
-
2
-
Spitfire
Description
Purpose/Overview:
Karate implementation based on test plans is created
Acceptance criteria:
- API Tests are created at https://github.com/folio-org/folio-integration-tests
- Test are shown as passed in Cucumber report.
TestRail: Results
Attachments
Issue Links
- has to be done after
-
FAT-192 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - KB credentials
-
- Closed
-
-
FAT-905 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Providers
-
- Closed
-
-
FAT-906 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Packages
-
- Closed
-
-
FAT-907 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Titles
-
- Closed
-
-
FAT-908 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Resources
-
- Closed
-
-
FAT-909 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Status/Proxy/Tags
-
- Closed
-
-
FAT-910 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Access types
-
- Closed
-
-
FAT-911 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - User Assignment
-
- Closed
-
-
FAT-912 mod-kb-ebsco-java: Create test plan to cover functionality with API Karate test - Usage Consolidation
-
- Closed
-
- is defined by
-
UXPROD-3320 Spitfire: Karate API Integration Testing (NFR) - Lotus work
-
- Closed
-