[UXPROD-4644] Update Karate Tests continued (Phase 5) Created: 31/Dec/23  Updated: 31/Dec/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Craig McNally Assignee: Craig McNally
Resolution: Unresolved Votes: 0
Labels: epam-eureka, eureka-phase5
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODROLESKC-71 Karate Tests - refactor vega/mod-circ... Open
is defined by MODROLESKC-72 Karate Tests - refactor spitfire/mod-... Open
is defined by MODROLESKC-73 Karate Tests - refactor prokopovych/m... Open
Development Team: Eureka
PO Rank: 0
RCA Group: TBD

 Description   

The existing karate tests in the FOLIO community provide a fair amount of integration test coverage.  Being able to run those against the enhanced platform developed by Eureka is important to ensure that we haven't broken anything.

 

In theory the test cases should need to be adjusted.  However, test setup and teardown typically involves interacting with OKAPI to create tenants, enable modules for tenants, etc.  This setup/teardown will need to be adjusted to work with the manager components introduced to replace OKAPI in the improved platform.

 

Scope:

  • Spike work to investigate current status of tests and test setup/teardown
  • Adjustment of the necessary (hopefully shared) test code.
    • Ideally this can be parameterized so we can support both modes of operations (talking to mgr components and to OKAPI)
  • Refactor tests so they're organized around applications instead of modules.   See https://ebscoinddev.atlassian.net/wiki/spaces/TEUR/pages/217780246/Integration+Karate+Test+Approach
    • Critical domains:
      • Circulation
      • Inventory
      • System (e.g. app-platform-minimal)
      • Acquisitions?
      • <Need to give this more thought, and look at which areas are the most stable>
  • Run the tests, identify and investigate failures

NOTE:  The expectation is that we should be able to run these tests against a local env, or cloud env.  E.g if running all of them, probably target an environment like nebf (or a refreshed/updated evrk).  If troubleshooting a particular test you may be able to run those tests locally.

 

TODO:

  1. Identify most critical applications, create stories for refactoring/migrating these
    1. Also look at the current test executions in the community - favor those which are are more stable
      1. See https://jenkins-aws.indexdata.com/job/Testing/job/Karate%20tests/652/cucumber-html-reports/overview-features.html 
  2. Create refactoring/migration stories
  3. Possibly let the community help with some of this work, but we shouldn't count on it.
  4. Provide a preliminary estimate once we know how many stories are in scope

Oleksii Kuzminov to try and identify which applications we should create stories for in this feature (See above for considerations)

Karate tests

https://jenkins-aws.indexdata.com/job/Testing/job/Scheduled%20Karate%20Tests/lastBuild/cucumber-html-reports/overview-features.html

Critical and part of platform-minimal and app-core

  • folijet/mod-source-record-storage (defer)
  • prokopovych/mod-inventory
  • spitfire/mod-notes (defer)
  • spitfire/mod-search
  • vega/mod-circulation
  • vega/mod-feesfines (defer)
  • volaris/mod-users 
  • firebird/mod-configuration (defer)

 

Non critical and part of platform-minimal and app-core

  • spitfire/mod-entities-links
  • folijet/mod-di-converter-storage
  • firebird/oaipmh
  • volaris/tags
  • volaris/mod-notify
  • volaris/mod-sender
  • volaris/mod-template-engine
  • volaris/password-validator

Source F77868: Update Karate Tests continued (Phase 5)
 


Generated at Fri Feb 09 00:41:27 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.