NFR: Create integration tests for key Data Import functionality using Karate (Lotus)
Description
Priority
Fix versions
Development Team
Folijet
Assignee
Ann-Marie Breaux
Ann-Marie Breaux(Deactivated)Solution Architect
None
NoneParent Field Value
None
Parent Status
None
continues
defines
is blocked by
is continued by
is defined by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Done
Details
Reporter
Taisiya TrunovaTaisiya TrunovaPO Rank
99Front End Estimate
Out of scopeBack End Estimate
XXL < 30 daysRelease
Lotus R1 2022TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Taisiya Trunova
Taisiya TrunovaPO Rank
99
Front End Estimate
Out of scope
Back End Estimate
XXL < 30 days
Release
Lotus R1 2022
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 11, 2021 at 1:50 PM
Updated February 28, 2022 at 3:56 PM
Resolved February 28, 2022 at 3:56 PM
TestRail: Cases
TestRail: Runs
Feature to create integration tests for main workflows in data import. This feature covers work done in Lotus. 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.
Continued from Kiwi
Preparation: Team will allocate time for the following
Setup Karate in modules (also link these issues to FAT-2) - DONE in
Define test plans (also link these issues to FAT-152)
Implement Karate tests (also link these issues to FAT-892)
https://folio-org.atlassian.net/wiki/display/FOLIJET/Karate+API+Integration+Testing
Scope for Lotus
Additional update workflows that were moved from Kiwi (so that we could add EDIFACT coverage into Kiwi)
Field protections and overriding field protections
Update only holdings and/or item based on MARC bib import
Continue coverage for creating profiles
Stretch or future feature for exceptions workflows, e.g.
Inventory record not created because mandatory data is missing
Holdings: missing permanent location
Item: missing permanent loan type, status
And document other exception/negative workflows that should be covered
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:
API Tests are created at https://github.com/folio-org/folio-integration-tests
Test run results are visible in TestRail: https://foliotest.testrail.io/index.php?/suites/overview/19
Automated regular runs are executed at https://jenkins-aws.indexdata.com/job/FOLIO_Reference_Builds/job/folio-integration/
Team's DoD updated to include API Karate tests integrated with TestRail