/
Dojo Eureka Karate Tests Hand-off Plan

Dojo Eureka Karate Tests Hand-off Plan

Owned by Andrei Moseev
Last updated: Apr 22, 2025
2 min read

Plan definition

This plan describes the process of transferring ownership over Eureka Karate tests from Dojo team back to the teams owning the modules.

Since the plan represents Dojo team point of view, the ownership transfer is named hand-off.

The goal is to enable module owners to smoothly trasition their Karate tests to Eureka and fully benefit from the effort taken by the Dojo team.

Process starting point

Tests hand-off will be started when all the modules owned by the same team are processed by the Dojo team according to Dojo defenition of done which consists of the following criteria:

  1. All Karate tests of the module are refactored to be executable against Eureka environments

  2. Test results against Eureka are the same as against OKAPI

  3. Some tests, mostly platform specific, might be exluded as they become obsolete for Eureka

  4. Changes passed code review, CI checks, merged to master-eureka branch

  5. Tests are verified with help of Jenkins pipeline

  6. Results posted to Jira comment, Jira ticket is closed

All common utility functions of Eureka Karate should be completed prior to hand-off initiation, though some late improvements cannot be fully avoided.

As an exception hand-off might be triggered when some modules owned by accepting team are not yet refactored due to some hard block.

Hand-off preparation

Following steps will be taken by the Dojo team before hand-off procedure

  1. Prepare a presentaion of the new Eureka Karate tests for the module owners

  2. Kindly ask modules owner team to put karate changes on hold

  3. Make final alighnement between OKAPI and Eureka and verify it

Hand-off procedure

  1. Meet with the module owners and present the new Eureka Karate tests

  2. Answer quesiotns

  3. Module owners take ownership over Eureka karate tests

  4. Disable OKAPI tests on master branch to prevent bug autogeneration as OKAPI tests get outdated

Post hand-off support

Dojo team will answer questions related to Eureka karate tests for 2 weeks after hand-off

Activities postponed to later phases of Eureka adoption

Some activities can only be started when all modules of all teams have migrated to Eureka:

  • Merging Eureka Karate to master

  • Decommission of OKAPI Jenkins pipelne

  • Enable bug autogeneration

Presentation content

  1. Common utility functions - Common Utility Functions in Eureka Karate

  2. Changes in module Karate tests - Module documentation

  3. Jenkins job runNightlyKarateEurekaTests [folioRancher » [MOVED] folioScheduledTesting] [Jenkins]

  4. Github branch https://github.com/folio-org/folio-integration-tests/tree/master-eureka

  5. IDE based Test Execution (README)

  6. Test time and stability

 

Related content